Re: Failures with gcd functions with GCC snapshots GCC and -O3 (?)

From: Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Michael Paquier <michael(at)paquier(dot)xyz>, Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de>
Subject: Re: Failures with gcd functions with GCC snapshots GCC and -O3 (?)
Date: 2021-06-05 14:31:32
Message-ID: alpine.DEB.2.22.394.2106051630270.1661092@pseudo
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


>>> serinus has been complaining about the new gcd functions in 13~:
>>
>> moonjelly, which also runs a bleeding-edge gcc, started to fail the same
>> way at about the same time. Given that none of our code in that area
>> has changed, it's hard to think it's anything but a broken compiler.
>
>> Maybe somebody should report that to gcc upstream?
>
> Yes.
>
> I will isolate a small case (hopefully) and do a report over week-end, after
> checking that the latest version is still broken.

Not needed in the end, the problem has disappeared with today's
gcc recompilation.

--
Fabien.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2021-06-05 15:02:49 Re: libpq debug log
Previous Message Ranier Vilela 2021-06-05 14:16:20 Re: Move pg_attribute.attcompression to earlier in struct for reduced size?