Re: [Linaro-TCWG-CI] gcc-16-1550-g9244ea4bf556: Failure on aarch64

2025-06-20 Thread Adhemerval Zanella Netto via Gcc-regression
I will take a look. On 20/06/25 07:16, Maxim Kuvyrkov wrote: > Hi Sam, > > Thanks for looking into this. > > Hi Adhemerval, > > Would you please look into how glibc should handle this? > > Thanks! > > -- > Maxim Kuvyrkov > https://www.linaro.org > >> On Jun 19, 2025, at 04:24, Sam James wro

Re: [Linaro-TCWG-CI] gcc-16-1550-g9244ea4bf556: Failure on aarch64

2025-06-20 Thread Maxim Kuvyrkov via Gcc-regression
Hi Sam, Thanks for looking into this. Hi Adhemerval, Would you please look into how glibc should handle this? Thanks! -- Maxim Kuvyrkov https://www.linaro.org > On Jun 19, 2025, at 04:24, Sam James wrote: > > Could you file a glibc bug for this please? It needs some analysis to > see if it'

Re: [Linaro-TCWG-CI] gcc-16-1550-g9244ea4bf556: Failure on aarch64

2025-06-18 Thread Sam James via Gcc-regression
Could you file a glibc bug for this please? It needs some analysis to see if it's an FP or not. There's actually a suppression for -Os already there: if (elem < table_size) { /* Compare the byte sequence but

[Linaro-TCWG-CI] gcc-16-1550-g9244ea4bf556: Failure on aarch64

2025-06-18 Thread ci_notify--- via Gcc-regression
Dear contributor, Our automatic CI has detected problems related to your patch(es). Please find some details below. In master-aarch64, after: | commit gcc-16-1550-g9244ea4bf556 | Author: Andrew MacLeod | Date: Mon Jun 16 15:41:47 2025 -0400 | | Snap subrange boundries to bitma