3 ms·
Yes, but the issue at hand isn't whether or not apps can or should be compiled to x32. That capability isn't going away (it happens entirely in userspace and i
by ajross 8y ago
Yes, but the issue at hand isn't whether or not apps can or should be compiled to x32. That capability isn't going away (it happens entirely in userspace and is basically just a recompiled set of libraries).
This is a discussion about whether the kernel itself wants to run using x32 mode, which is arguably much less useful. Such a system would be limited to 4G of physical memory, etc... There aren't that many such systems left in the x86 world (that run Linux, anyway -- I'm literally working on an x86_64 port for Zephyr now, and it uses x32).
- pantalaimon 8y agoNo this is about running userspace x32 programs that will make x32 syscalls with 32bit pointers. Such kernel will run x86 binaries (in compat mode), x86_64 binaries and x86_32 ones.
- jabl 8y ago> Yes, but the issue at hand isn't whether or not apps can or should be compiled to x32. That capability isn't going away (it happens entirely in userspace and is basically just a recompiled set of libraries). If the kernel removes X32 support, I guess it won't take long for toolchains to remove it either. Why should they pay the maintenance burden of it if nobody uses it? > This is a discussion about whether the kernel itself wants to run using x32 mode, No, the kernel has never supported running in X32 mode itself. This is about the compatibility syscalls allowing a X32 userspace with a x86-64 kernel.