Were they emulating the x86 code in realtime, or pre-translating it to RISC-V in the way that Apple’s Rosetta 2 does for ARM? If the former, that is indeed impressive performance.
The original blog post (linked in the article) refers to this as a DynaRec, i.e. a dynamic recompiler. So it’s not exactly emulating, but nor is it the ahead-of-time recompilation that Rosetta 2 can do.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: [email protected]
No game suggestions, friend requests, surveys, or begging.
No Let’s Plays, streams, highlight reels/montages, random videos or shorts.
No off-topic posts/comments, within reason.
Use the original source, no clickbait titles, no duplicates.
(Submissions should be from the original source if possible, unless from paywalled or non-english sources.
If the title is clickbait or lacks context you may lightly edit the title.)
I think thats a pretty big achievement that it runs at all on the wrong instruction set. RISC-V development really seems to have come far
I’d love to know the power draw, the article doesn’t mention it (that I could see).
It’s pretty nuts to be able to take something as complex as a video game and to run it on unintended hardware.
PS3 next?
If rpcs3 uses a dynarec, then one would have to specifically be made for RISC-V. The interpreter can probably already run right now.
Were they emulating the x86 code in realtime, or pre-translating it to RISC-V in the way that Apple’s Rosetta 2 does for ARM? If the former, that is indeed impressive performance.
The original blog post (linked in the article) refers to this as a DynaRec, i.e. a dynamic recompiler. So it’s not exactly emulating, but nor is it the ahead-of-time recompilation that Rosetta 2 can do.
I don’t even care. The fact that we’re at a point where it runs means a whole bunch of "step one"s have been succefully taken.
Believe it or not, the article answers that question. The linked blog post from the devs has even more detail.