Problem building latest jdk9-arm3264

[Simon Nash]

Simon Nash wrote:
> Bob Vandette wrote:
>> Looks like you’ve got a gcc issue.
>>
>> Did you apply the patch that I sent out for review?
>>
>> http://cr.openjdk.java.net/~bobv/8168909/webrev
>>
>> I’ll try building the lastest jdk9-arm3264 without that patch to see 
>> if I have the same issue.
>>
>> Bob.
>>
> Bob,
> Thanks for the quick reply.  Here is my output from gcc -v:
> 
> Using built-in specs.
> COLLECT_GCC=gcc
> COLLECT_LTO_WRAPPER=/usr/lib/gcc/arm-linux-gnueabihf/4.9/lto-wrapper
> Target: arm-linux-gnueabihf
> Configured with: ../src/configure -v --with-pkgversion='Raspbian 
> 4.9.2-10' --with-bugurl=file:///usr/share/doc/gcc-4.9/README.Bugs 
> --enable-languages=c,c++,java,go,d,fortran,objc,obj-c++ --prefix=/usr 
> --program-suffix=-4.9 --enable-shared --enable-linker-build-id 
> --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix 
> --with-gxx-include-dir=/usr/include/c++/4.9 --libdir=/usr/lib 
> --enable-nls --with-sysroot=/ --enable-clocale=gnu 
> --enable-libstdcxx-debug --enable-libstdcxx-time=yes 
> --enable-gnu-unique-object --disable-libitm --disable-libquadmath 
> --enable-plugin --with-system-zlib --disable-browser-plugin 
> --enable-java-awt=gtk --enable-gtk-cairo 
> --with-java-home=/usr/lib/jvm/java-1.5.0-gcj-4.9-armhf/jre 
> --enable-java-home 
> --with-jvm-root-dir=/usr/lib/jvm/java-1.5.0-gcj-4.9-armhf 
> --with-jvm-jar-dir=/usr/lib/jvm-exports/java-1.5.0-gcj-4.9-armhf 
> --with-arch-directory=arm --with-ecj-jar=/usr/share/java/eclipse-ecj.jar 
> --enable-objc-gc --enable-multiarch --disable-sjlj-exceptions 
> --with-arch=armv6 --with-fpu=vfp --with-float=hard 
> --enable-checking=release --build=arm-linux-gnueabihf 
> --host=arm-linux-gnueabihf --target=arm-linux-gnueabihf
> Thread model: posix
> gcc version 4.9.2 (Raspbian 4.9.2-10)
> 
> I have not applied your webrev patch yet because I am trying to take 
> this one step at a time.
> 
In case anyone else has this problem, I have found a workaround.  The problem is
caused by the use of precompiled headers together with -O3.  If I add the option
--disable-precompiled-headers to the .configure command, the build completes
successfully.  This appears to be similar to this bug:
  https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63319

Simon