On Mon, Nov 28, 2016 at 2:34 PM, Gustavo Romero
wrote:
> Hi Volker,
>
> On 25-11-2016 14:32, Volker Simonis wrote:
>> On Fri, Nov 25, 2016 at 3:51 PM, Andrew Haley wrote:
>>> On 22/11/16 09:57, Andrew Haley wrote:
On 22/11/16 00:41, Gustavo Romero wrote:
> Do you know if the gap between
Hi Volker,
On 25-11-2016 14:32, Volker Simonis wrote:
> On Fri, Nov 25, 2016 at 3:51 PM, Andrew Haley wrote:
>> On 22/11/16 09:57, Andrew Haley wrote:
>>> On 22/11/16 00:41, Gustavo Romero wrote:
Do you know if the gap between Math and StrictMath is also huge on aarch64?
>>>
>>> I'll try to
On Fri, Nov 25, 2016 at 3:51 PM, Andrew Haley wrote:
> On 22/11/16 09:57, Andrew Haley wrote:
>> On 22/11/16 00:41, Gustavo Romero wrote:
>>> Do you know if the gap between Math and StrictMath is also huge on aarch64?
>>
>> I'll try to have a look.
>
> The gap is just the same as PPC.
>
I've alre
On 22/11/16 09:57, Andrew Haley wrote:
> On 22/11/16 00:41, Gustavo Romero wrote:
>> Do you know if the gap between Math and StrictMath is also huge on aarch64?
>
> I'll try to have a look.
The gap is just the same as PPC.
Andrew.
On 22/11/16 00:41, Gustavo Romero wrote:
> Do you know if the gap between Math and StrictMath is also huge on aarch64?
I'll try to have a look.
Andrew.
On 11/21/16 4:27 PM, Gustavo Romero wrote:
Hi Joe,
On 17-11-2016 19:33, 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 and contro
Hello,
On 11/21/2016 4:34 PM, Gustavo Romero wrote:
Hi Chris,
On 17-11-2016 19:48, Chris Plummer wrote:
The fdlibm code relies on aliasing a two-element array of int with a double to
do bit-level reads and writes of floating-point values. As I understand it, the
C spec allows compilers to a
Hi Derek,
On 17-11-2016 20:47, White, Derek wrote:
> 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 t
Hi Chris,
On 17-11-2016 19:48, Chris Plummer wrote:
>> The fdlibm code relies on aliasing a two-element array of int with a double
>> to do bit-level reads and writes of floating-point values. As I understand
>> it, the C spec allows compilers to assume
>> values of different types don't overlap
Hi Joe,
On 17-11-2016 19:33, 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 and control regarding floating-point se
a.net;
hotspot-...@openjdk.java.net; core-libs-...@openjdk.java.net
Cc: build-dev
Subject: 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,
>
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
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
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
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
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
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
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
Adding in build-dev as they need to scrutinize all build changes.
David
On 17/11/2016 11:45 AM, Gustavo Romero wrote:
Hi,
Currently, optimization for building fdlibm is disabled, except for the
"solaris" OS target [1].
As a consequence on PPC64 (Linux) StrictMath methods like, but not limited
19 matches
Mail list logo
