-
Notifications
You must be signed in to change notification settings - Fork 64
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 aarch64 support to the SH2 dynarec #87
Comments
They are what 20mhz? The interpreter must be terribly slow... Also isn't ARMv8 capable of running 32b arm code? |
ARMv8 can, switch, or at least libnx can't. |
I don't have a ton of time, but given enough interest, perhaps I could add an aarch64 emitter to the dynarec in reicast and add it to picodrive as well. |
How much time would you estimate such a project would take? |
A full aarch64 emitter to satisfy reicast would take a few weeks, updating the recompiler and testing would take several more per target. Prob ~ 2-3mo |
Would this be satisfactory: https://github.com/irixxxx/picodrive |
@irixxxx I will check it out and try it on the Switch, if it's satisfactory and you want the bounty, sure go claim afterwards. |
Current state of aarch64 dynarec? |
no change |
Any updates for this? |
Nope. No change. |
With current core It should be enabled on all build targets with aarch64 architecture. Any feedback? |
It doesn't seem to be enabled for Switch (libnx)? |
Right now, the SH2 dynarec (used for Sega 32X) only works for the following platforms:
Every other architecture right now has to fall back on an interpreter core which is not fast enough for many low powered Aarch64 SoCs, including the one on the Nintendo Switch.
This bounty is for the purpose of adding an Aarch64 dynarec backend as well to the existing SH2 dynarec. Perfomance needs to be comparable or better than the existing dynarecs.
https://www.bountysource.com/issues/64126757-missing-feature-ifdef-__aarch64__-in-cpu-sh2-compiler-c
Bounty has been started and starts at $50.
Edited by: twinaphex
The text was updated successfully, but these errors were encountered: