On Fri, 3 Nov 2023 at 13:51, Ben Sherman wrote:
>
> > This was https://gcc.gnu.org/PR109703 (and several duplicates) and
> > should already be fixed in all affected branches. Where are you seeing
> > this?
>
> I saw this on 13.1.0 and could not find the bug report or fix for it, so I
> didn't real
Jonathan Wakely writes:
> On Thu, 2 Nov 2023 at 19:58, Ben Sherman
> wrote:
>>
>> Tested on x86_64-pc-linux-gnu, please let me know if there's anything
>> else needed. I haven't contributed before and don't have write access, so
>> apologies if I've missed anything.
>
> This was https://gcc.g
> This was https://gcc.gnu.org/PR109703 (and several duplicates) and
> should already be fixed in all affected branches. Where are you seeing
> this?
I saw this on 13.1.0 and could not find the bug report or fix for it, so I
didn't realize it had already been fixed. Sorry about that.
This e
On Thu, 2 Nov 2023 at 19:58, Ben Sherman wrote:
>
> Tested on x86_64-pc-linux-gnu, please let me know if there's anything
> else needed. I haven't contributed before and don't have write access, so
> apologies if I've missed anything.
This was https://gcc.gnu.org/PR109703 (and several duplicates)
