The world would be a better place if the current x86 32-bit ABI was replaced by "x32" https://en.wikipedia.org/wiki/X32_ABI but it's looking unlikely that we will get there. For starters, all compilers must be rewritten to target x32, and that includes the jdk jits. And that's a big project, one for compiler writers, not autoconf hackers. Whoever is trying to make x32 happen should also try to take this on.
On Wed, Oct 21, 2015 at 11:39 PM, Volker Simonis <volker.simo...@gmail.com> wrote: > I only now took a look at the what x86_64-linux-gnux32 really means > (thanks Andrew for providing the link). > > So independently of the discussed build issues I doubt that this > currently really makes sense for the OpenJDK. The VM is simply not > aware of the new ABI so all the generated code (interpreter, JIT) > won't use the extra registers anyway. I also suspect there could be > calling conventions problems from generated to native code. Making all > this work is a much bigger effort than just passing the right flags to > the compiler. > > On Tue, Oct 20, 2015 at 3:06 PM, Andrew Haley <a...@redhat.com> wrote: > > On 10/20/2015 01:57 PM, Magnus Ihse Bursie wrote: > >> What does x86_64-linux-gnux32 imply? Some sort of mix between 32 and > 64-bit? > > > > I think that's a 32-bit ABI running on a 64-bit processor. > > > > https://en.wikipedia.org/wiki/X32_ABI > > > > If so, I'm surprised it works at all. > > > > Andrew. > > >
