hardcoding -m32/-m64 is more harmful than using the toolchain defaults

[Volker Simonis]

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 <aph at 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.
>