RFR: AARCH64: Top-level JDK changes

Omair Majid omajid at redhat.com
Mon Nov 10 17:45:37 UTC 2014


* Christian Thalinger <christian.thalinger at oracle.com> [2014-11-07 13:11]:
> > 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:
> >> 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?

I had to do a similar fix for zero on arm32:
http://hg.openjdk.java.net/jdk8/jdk8/rev/1dfcc874461e#l2.7

Perhaps that can be re-used here?

Thanks,
Omair

-- 
PGP Key: 66484681 (http://pgp.mit.edu/)
Fingerprint = F072 555B 0A17 3957 4E95  0056 F286 F14F 6648 4681


More information about the jdk9-dev mailing list