Re: PPC64: Poor StrictMath performance due to non-optimized compilation

Hello, Overall this looks reasonable to me. However, if we want to introduce a new possible tuple for specifying compilation flags to SetupNativeCompilation, we (the build team) would prefer if we used OPENJDK_TARGET_CPU instead of OPENJDK_TARGET_CPU_ARCH. /Erik On 2016-11-17 03:31, David H

RFR: JDK-8169860 Clean up and unify the refactored Javadoc generation

This is a follow-up to JDK-8168772 . In that bug, the goal was to just refactor the generation, and keep output identical, by whatever means neccessary. This bug takes the final step, and cleans up the code. The changes will have the following

Re: PPC64: Poor StrictMath performance due to non-optimized compilation

Hello, On 11/16/2016 5:45 PM, Gustavo Romero wrote: Hi, Currently, optimization for building fdlibm is disabled, except for the "solaris" OS target [1]. The reason for that is because historically the Solaris compilers have had sufficient discipline and control regarding floating-point sema

Re: PPC64: Poor StrictMath performance due to non-optimized compilation

Hi David, On 17-11-2016 00:31, David Holmes wrote: > Adding in build-dev as they need to scrutinize all build changes. Thanks a lot. Regards, Gustavo

Re: PPC64: Poor StrictMath performance due to non-optimized compilation

Hi Erik, On 17-11-2016 07:17, Erik Joelsson wrote: > Overall this looks reasonable to me. However, if we want to introduce a new > possible tuple for specifying compilation flags to SetupNativeCompilation, we > (the build team) would prefer if we used > OPENJDK_TARGET_CPU instead of OPENJDK_TARG

Re: PPC64: Poor StrictMath performance due to non-optimized compilation

Hi Joe, Thanks a lot for your valuable comments. On 17-11-2016 15:35, joe darcy wrote: >> Currently, optimization for building fdlibm is disabled, except for the >> "solaris" OS target [1]. > > The reason for that is because historically the Solaris compilers have had > sufficient discipline an

Re: PPC64: Poor StrictMath performance due to non-optimized compilation

Hi Gustavo, On 11/17/2016 10:31 AM, Gustavo Romero wrote: Hi Joe, Thanks a lot for your valuable comments. On 17-11-2016 15:35, joe darcy wrote: Currently, optimization for building fdlibm is disabled, except for the "solaris" OS target [1]. The reason for that is because historically the S

Re: PPC64: Poor StrictMath performance due to non-optimized compilation

On 11/17/16 1:33 PM, joe darcy wrote: Hi Gustavo, On 11/17/2016 10:31 AM, Gustavo Romero wrote: Hi Joe, Thanks a lot for your valuable comments. On 17-11-2016 15:35, joe darcy wrote: Currently, optimization for building fdlibm is disabled, except for the "solaris" OS target [1]. The reason

RE: PPC64: Poor StrictMath performance due to non-optimized compilation

Hi Joe, Although neither a floating point expert (as I think I've proven to you over the years), or a gcc expert, I checked with our in-house gcc expert and got this following answer: "Yes using -fno-strict-aliasing fixes the issues. Also there are many forks of fdlibm which has this