RFR: AARCH64: Top-level JDK changes
Christian Thalinger
christian.thalinger at oracle.com
Fri Nov 7 18:21:31 UTC 2014
> On Nov 7, 2014, at 10:10 AM, Christian Thalinger <christian.thalinger at oracle.com> wrote:
>
>>
>> On Nov 7, 2014, at 9:55 AM, Andrew Haley <aph at redhat.com> wrote:
>>
>> On 11/07/2014 05:42 PM, Christian Thalinger wrote:
>>>
>>>> On Nov 7, 2014, at 9:21 AM, Andrew Haley <aph at redhat.com> wrote:
>>>>
>>>> The first patch: top-level build machinery changes.
>>>>
>>>> http://cr.openjdk.java.net/~aph/8064357-rev-1/ <http://cr.openjdk.java.net/~aph/8064357-rev-1/>
>>>
>>> common/autoconf/flags.m4
>>>
>>> + aarch64)
>>> + ZERO_ARCHFLAG=""
>>> + ;;
>>>
>>> Why is this required on aarch64 but not all the other architectures?
>>
>> I think it's because GCC rejects "-m64”.
>
> That’s interesting. I thought -m<archbits> is some kind of common flag that works on all architectures. Can someone verify this?
This page doesn’t list it (while x86, SPARC, and PowerPC pages do):
https://gcc.gnu.org/onlinedocs/gcc/AArch64-Options.html <https://gcc.gnu.org/onlinedocs/gcc/AArch64-Options.html>
I guess it’s good then.
>
>>
>> Andrew.
More information about the jdk9-dev
mailing list