> Am 03.02.2023 um 19:47 schrieb Vineet Gupta :
>
>
>> On 2/2/23 23:36, Richard Biener wrote:
>> There's a CLOSED INVALID bug in bugzilla
>> about the povray failure as well.
>
> Thx for the pointer ! For the record it is
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107021
>
> > The quest
On 2/2/23 23:36, Richard Biener wrote:
There's a CLOSED INVALID bug in bugzilla
about the povray failure as well.
Thx for the pointer ! For the record it is
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107021
> The question is what to do with 511.povray_r as we want to support
SPECs with -O
On Fri, Feb 3, 2023 at 12:39 AM Vineet Gupta wrote:
>
> Hi,
>
> I've noticed SPEC 2017, 511.pov failing for RV64 on bleeding edge gcc.
> This is with -Ofast -march=rv64gcv_zba_zbb_zbc_zbs.
> Problem also happens with -O3 -ffast-math (and goes away with fast-math
> removed)
>
> I've bisected it to
On 2/2/23 15:38, Vineet Gupta wrote:
Hi,
I've noticed SPEC 2017, 511.pov failing for RV64 on bleeding edge gcc.
This is with -Ofast -march=rv64gcv_zba_zbb_zbc_zbs.
Problem also happens with -O3 -ffast-math (and goes away with
fast-math removed)
I've bisected it to b7fd7fb50111 ("frange: dr
Hi,
I've noticed SPEC 2017, 511.pov failing for RV64 on bleeding edge gcc.
This is with -Ofast -march=rv64gcv_zba_zbb_zbc_zbs.
Problem also happens with -O3 -ffast-math (and goes away with fast-math
removed)
I've bisected it to b7fd7fb50111 ("frange: drop endpoints to min/max
representable nu
