A general purpose Apple Silicon layer for x86-64 PCs
84 points by iceboundrock 7 hours ago | 34 comments

iceboundrock 7 hours ago
A general purpose Apple Silicon layer for x86-64 PCs. It is a UEFI boot program with an arm64-to-x86-64 translator, a Metal driver for NVIDIA GPUs and a model of Apple silicon hardware. macOS and most apps start, but it is slow and needs much more testing, as of v0.1.0
reply
stingraycharles 4 hours ago
Is the intent to support running macOS on it, or rather for e.g. Linux that targets Apple Silicon?
reply
perfsakuya 3 hours ago
To support running the Apple Silicon version of macOS on x86-64 PCs.
reply
userbinator 2 hours ago
There was a lot of discussion around the time the M1 came out about how it would be the end of Hackintoshes, but it seems the Hackintoshers just won't give up (and now they have the help of AI.)
reply
yjftsjthsd-h 6 hours ago
So, basically an emulator layer that doesn't need a host OS? (I'm not really interested in running Darwin, but that's a cool concept)
reply
userbinator 2 hours ago
I guess one could call it a "bare-metal/type 1 emulator" much like VMs can run in a "bare-metal/type 1 hypervisor".
reply
cromka 6 hours ago
"An ahead-of-time and just-in-time compiler translates arm64e code to x86-64."

No, not the same, actually. It's more of a Rosetta, but other way round, if I understand this right.

reply
yjftsjthsd-h 5 hours ago
Rosetta is an emulator (or, I suppose, a series of emulators), i.e. a piece of software that makes a computer pretend to be another kind of computer. This is also a bit of lower level software that makes a (x86_64) computer pretend to be a different kind of computer (aarch64), in this case, by AoT and JIT translation, though that's an implementation detail. What distinction are you trying to make?
reply
stavros 3 hours ago
This doesn't emulate a computer so that code in another architecture can run, it translates the other architecture'a code to native code. It's a small difference, but I guess it is a difference.
reply
throwaway27448 3 hours ago
Is this not how qemu works? Is rosetta not considered an emulation layer? For all its name suggests otherwise, I would certainly refer to wine as an emulator, and it also uses these techniques.
reply
zbentley 3 hours ago
Not to be That Guy, but WINE doesn't use those techniques, and thus isn't an emulator.

It lightly translates binary formats (Windows executables) into Linux-compatible executable code, and then runs that code against libraries that implement Windows APIs in terms of Linux underneath. It's not an emulator in the same way that your libc isn't emulating lockf(3) in terms of fcntl(2) underneath. In web-dev parlance, we'd call WINE a polyfill.

Rosetta and QEMU on the other hand are emulators--emulators, in this instance, being a term of art that implies interpreting bespoke meaning from machine code instructions written in another program. Some emulators translate instructions 1:1, some have optimized stencils, some (like Rosetta) have kernel support for emulating very quickly, and some (maybe like Rosetta; sources disagree) also have hardware support as well.

reply
userbinator 2 hours ago
I believe WINE doesn't actually translate any instructions; it's a Windows PE loader and a bunch of libraries that implement Windows APIs using Linux equivalents.
reply
throwaway27448 2 hours ago
How does it handle stuff like syscalls without altering the executed code?
reply
pcwalton 47 minutes ago
Windows apps don't use syscalls directly; they call into kernel32.dll, which is convenient for Wine. (Microsoft enforces this by scrambling the syscall numbers on OS updates [1].)

[1]: https://j00ru.vexillium.org/syscalls/nt/64/

reply
aunderscored 2 hours ago
It installs handlers. I don't have the exact name but there's support in the kernel to redirect syscalls to a Userland process
reply
leidenfrost 3 hours ago
Wine as a polyfill makes so much more sense
reply
throwaway27448 3 hours ago
> It lightly translates binary formats (Windows executables) into Linux-compatible executable code,

Does this not involve transpilation? I guess I was grouping that in under dynamic recompilation and AOT techniques.

Regardless, I don't think that there's a benefit from defining emulation from an implementation rather than an empirical perspective. If it runs a chunk of code as if it were in a different environment, I'm kind of ok to call it an emulator. To the sibling's point, a polyfill would also fit as an emulation layer here.

reply
ecnahc515 56 minutes ago
Not necessarily. It could just rewrite the outer portion to be an ELF loader that then calls into a runtime that actually shims the syscalls for example. I don't think WINE does exactly this but it's not really transpiling either.
reply
jamesy0ung 5 hours ago
I noticed Golden Gate still ships with an x86_64 kernel (not kernelcache), I wonder if this is any useful

james@Jamess-MacBook-Pro ~ % sw_vers ProductName: macOS ProductVersion: 27.2.1 BuildVersion: 26B131 james@Jamess-MacBook-Pro ~ % file /System/Library/Kernels/kernel /System/Library/Kernels/kernel: Mach-O 64-bit executable x86_64 james@Jamess-MacBook-Pro ~ % strings /System/Library/Kernels/kernel | grep "Darwin" @(#)VERSION: Darwin Kernel Version 27.2.0: Wed Oct 14 23:40:09 PDT 2026; root:xnu-13432.41.4~25/RELEASE_X86_64 Darwin Kernel Version 27.2.0: Wed Oct 14 23:40:09 PDT 2026; root:xnu-13432.41.4~25/RELEASE_X86_64 Darwin

reply
vintagedave 5 hours ago
This is fascinating. If x64 isn’t supported in Golden Gate why is this present?
reply
ykl 3 hours ago
Rosetta 2 is still supported, and the way Rosetta 2 works requires that various system components that x64 apps might depend on also be available in x64. x64 code that is running as arm64 translated by Rosetta 2 can’t call into native arm64 code due to ABI differences, so Rosetta 2 must translate the x64 version of system libraries as well.

My impression was that this did not require the kernel though, just system frameworks, so I don’t know why there’s a full x64 kernel in there!

reply
stingraycharles 4 hours ago
Not saying this is the reason, but we build and test and release our software on platforms nobody uses, as it catches rare compiler / memory / UB bugs we otherwise wouldn’t have (eg win32 and FreeBSD)
reply
1over137 4 hours ago
Lots of people use FreeBSD :)
reply
ndiddy 4 hours ago
Reminds me of how some of the dev versions of Snow Leopard still boot on PowerPC.
reply
schmeichel 6 hours ago
Huge. I have been desperately looking for a project like this to be able to use https://github.com/seedds/nxnative to be able to play my copy of BOTW on IOS. Thank you for sharing this, I will be trying it this evening.
reply
sneurlax 6 hours ago
Is this really needed? I got it working on macOS pretty easily without this. It's all in private repos tho, not exactly easy to share by URL unless you're willing to sign up for a gitea.
reply
rbanffy 6 hours ago
Sounds like a great use for those new Epyc processors with 256 cores…
reply
orionblastar 7 hours ago
This repository needs a star and a follow. It stops Intel Macs from becoming obsolete, but it is slow and buggy.
reply
code_duck 5 hours ago
Apple still supports the latest ones up to Tahoe, and probably security updates for a few years. You can install Windows 10 (no idea about 11) but that is only updated through next year. After that, there's Linux, of course.
reply
1over137 4 hours ago
macOS does get some security updates for the non-latest version, but it does not get all security updates.

https://arstechnica.com/gadgets/2021/11/psa-apple-isnt-actua...

reply
rbanffy 6 hours ago
I don’t think there is anything that can make Intel Macs not obsolete. Embrace it - that’s their charm and you should use them as they were intended to be used, and experience them as they were designed, as artifacts of their time.
reply
iceboundrock 6 hours ago
I installed CachyOS on my MacBook 16,1, and it feels much faster than with macOS, but the D side is still hot though.
reply
LeFantome 4 hours ago
No thank you. They can sit in a museum 30 years from now. Today, they are still amazing and productive machines (once you get macOS off them).
reply
bigyabai 3 hours ago
Many (most?) Intel Macs still receive microcode updates, Mesa support and recent kernel changes.

The only obsolete part is macOS, which is removable.

reply