Hector Martin

The best Rosetta 2 can do here is just scan the executable ahead of time, and try to JIT everything it *guesses* it might need later ahead of time. It won't know until the app runs whether it guessed right. It's an emulator. A nice, well engineered emulator.

(Alternately, if you subscribe to "emulators don't translate, they interpret", then qemu and Dolphin aren't emulators either)

Wine Is Not an Emulator, but wine works under Rosetta 2, which is. Is Rosetta 2 statically translating Windows apps to macOS ARM? Obviously not :-) Is Rosetta 2 JITting Windows apps when run through Wine? Sure! Is it caching those translations? We don't know! Open question.

Why are you so sure it’s not statically translating?

Because that's not a solvable problem, as I've said before. Also it would involve linking wine into windows executable to build statically linked(?) osx executables and... what? No, none of that makes any practical sense.

Do you see how it could be a *mostly* ahead of time translator?

That's exactly what I said, it does cache warming. The point is, it isn't a new paradigm. Using a Shiny New Word like "translator" is marketing speak to make people think it's revolutionary. It isn't. It's just good.

I mean....pre-translating literally the entire __TEXT segment feels like more than cache warming to me.