2026-09-21 15:57 UTC
@joe@f.duriansoftware.com Alright so from my quick n dirty test, I think I have an answer: a 64-bit process on 10.4 *can* i386_set_ldt a 32-bit code segment (raw syscall, no libSystem wrapper) and lcall into it once you shrink the 4GB pagezero. But the kernel still treats the task as 64-bit. So hosting AppKit that way is starting to smell like some haunted WoW64-style thunk layer and the thought of building that gives me a nosebleed
Replies (1)
-
@joe@f.duriansoftware.com 2026-09-21 16:19
@samhenrigold@hachyderm.io if the kernel and WindowServer don't block you outright, i was thinking you could set up this environment to host a mostly-32-bit process, where you run normal 32-bit frameworks and app code, but with the ability to also host in-process the backend bits that need to be 64-bit. you'd need to trampoline the API surface for those backend bits, but you could share memory at least, and that might be a bit more efficient than doing IPC with a separate 64-bit process