Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add back our older VFPU approximations, as fallbacks if the table files are missing #17228

Merged
merged 4 commits into from
Apr 4, 2023

Conversation

hrydgard
Copy link
Owner

@hrydgard hrydgard commented Apr 3, 2023

PR #16984 added more accurate versions of these functions, but they require large lookup tables stored in assets/.

If these files are missing, PPSSPP would simply crash, which isn't good. It's very common for assets files to be missing when running as a libretro core, because those users just don't seem to be in the habit of copying these when they install a core.

We should probably try to warn the user somehow that these files are missing, though...

This also fixes deployment of the table files on UWP builds (some additional files snuck in too, without me explicitly adding them.. might as well let them, they're just gonna get auto-added again later and don't do any harm)

…sing.

PR #16984 added more accurate versions of these functions, but they require
large lookup tables stored in assets/.

If these files are missing, PPSSPP would simply crash, which isn't good.

We should probably try to warn the user somehow that these files are
missing, though...
@hrydgard hrydgard added the Libretro Issue on Libretro but not all ports. label Apr 3, 2023
@hrydgard hrydgard added this to the v1.15.0 milestone Apr 3, 2023
@hrydgard hrydgard added CPU emulation and removed Libretro Issue on Libretro but not all ports. labels Apr 3, 2023
@hrydgard hrydgard mentioned this pull request Apr 3, 2023
5 tasks
@GABO1423
Copy link
Contributor

GABO1423 commented Apr 3, 2023

The CoreUWP.vcxproj file has the ForcedInclude double line bloat again :/

EDIT: For the missing assets, we could just add them in a similar way I did for the missing shader, debugger, and other assets files too (EDIT 2: nvm, saw they were added)

@hrydgard
Copy link
Owner Author

hrydgard commented Apr 3, 2023

It's MSVC screwing it up, gah. Not sure it's worth removing since it keeps coming back, but did it anyway.

@GABO1423
Copy link
Contributor

GABO1423 commented Apr 3, 2023

Not sure it's worth removing since it keeps coming back, but did it anyway.

Guess we'll just give up on it next time it comes back. Maybe it's more worthwhile to edit the files manually in the long term? That way the MSVC quirks aren't a factor?

Copy link
Collaborator

@unknownbrackets unknownbrackets left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's a bit of a shame that it's on each call, maybe would be better to have a func pointer or something. But probably not a big deal, considering the overall overheads in the func.

-[Unknown]

@unknownbrackets unknownbrackets merged commit 5c1e66a into master Apr 4, 2023
@unknownbrackets unknownbrackets deleted the vfpu-fallbacks branch April 4, 2023 06:53
@hrydgard
Copy link
Owner Author

hrydgard commented Apr 4, 2023

Yeah, I think I'll re-do how this works. But this at least fixes the crash.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants