RFR(s) 8170153: PPC64: Poor StrictMath performance due to non-optimized compilation (original) (raw)
Erik Joelsson erik.joelsson at oracle.com
Fri Nov 25 14:06:27 UTC 2016
- Previous message: RFR(s) 8170153: PPC64: Poor StrictMath performance due to non-optimized compilation
- Next message: RFR(s) 8170153: PPC64: Poor StrictMath performance due to non-optimized compilation
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Looks good.
/Erik
On 2016-11-25 14:32, Volker Simonis wrote:
Hi Gustavo,
we've realized that we have exactly the same problem on Linux/s390 so I hope you don't mind that I've updated the bug and the webrev to also include the fix for Linux/s390: http://cr.openjdk.java.net/~simonis/webrevs/2016/8170153.top/ http://cr.openjdk.java.net/~simonis/webrevs/2016/8170153.jdk/ https://bugs.openjdk.java.net/browse/JDK-8170153 The top-level change stays the same (I've only added the current reviewers) and for the jdk change I've just added Linux/s390 as another platform which can compile fdlibm with HIGH optimization. Thanks, Volker On Wed, Nov 23, 2016 at 4:33 PM, Gustavo Romero <gromero at linux.vnet.ibm.com> wrote: Hi Erik,
On 23-11-2016 12:29, Erik Joelsson wrote: Build changes look ok.
In CoreLibraries.gmk, I think it would have been ok to keep the conditional checking (OPENJDKTARGETCPUARCH, ppc), but this certainly works too. Thanks a lot for reviewing the change. Regards, Gustavo
- Previous message: RFR(s) 8170153: PPC64: Poor StrictMath performance due to non-optimized compilation
- Next message: RFR(s) 8170153: PPC64: Poor StrictMath performance due to non-optimized compilation
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]