Re: [Linaro-TCWG-CI] gcc-16-1550-g9244ea4bf556: Failure on aarch64
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's an FP or not.
>
> There's actually a suppression for -Os already there:
>
>if (elem < table_size)
> {
>/* Compare the byte sequence but only if
> this is not part of a range. */
>
>/* The compiler might warn that idx may be
> used uninitialized, however it will be
> reached iff elem < table_size which means
> that it was properly set in the loop
> above. */
>DIAG_PUSH_NEEDS_COMMENT;
>DIAG_IGNORE_Os_NEEDS_COMMENT (8,
> "-Wmaybe-uninitialized");
>if (! is_range
>
> # if WIDE_CHAR_VERSION
>&& __wmemcmp (n, &wextra[1], c1) == 0
> # else
>&& memcmp (n, &extra[idx + 1], c1) == 0
> # endif
>)
> {
>n += c1 - 1;
>goto matched;
> }
>DIAG_POP_NEEDS_COMMENT;
> ___
> linaro-toolchain mailing list -- linaro-toolch...@lists.linaro.org
> To unsubscribe send an email to linaro-toolchain-le...@lists.linaro.org
Regressions on native/releases/gcc-14 at commit r14-11855 vs commit r14-11853 on Linux/x86_64
Regressions on releases/gcc-14 at commit r14-11855 vs commit r14-11853 on Linux/x86_64 New failures: FAIL: c-c++-common/tsan/free_race2.c -O0 output pattern test FAIL: c-c++-common/tsan/free_race2.c -O2 output pattern test FAIL: c-c++-common/tsan/mutexset1.c -O0 output pattern test FAIL: c-c++-common/tsan/mutexset1.c -O2 output pattern test FAIL: c-c++-common/tsan/pr65400-1.c -O2 output pattern test FAIL: c-c++-common/tsan/race_on_barrier2.c -O2 output pattern test FAIL: c-c++-common/tsan/race_on_mutex2.c -O0 output pattern test FAIL: c-c++-common/tsan/thread_leak.c -O0 execution test FAIL: g++.dg/tsan/aligned_vs_unaligned_race.C -O0 output pattern test FAIL: g++.dg/tsan/aligned_vs_unaligned_race.C -O2 output pattern test FAIL: g++.dg/tsan/atomic_free2.C -O0 output pattern test FAIL: g++.dg/tsan/atomic_free2.C -O2 output pattern test FAIL: g++.dg/tsan/atomic_free.C -O0 output pattern test FAIL: g++.dg/tsan/benign_race.C -O0 execution test FAIL: g++.dg/tsan/benign_race.C -O2 execution test FAIL: g++.dg/tsan/cond_race.C -O0 output pattern test FAIL: g++.dg/tsan/default_options.C -O2 execution test FAIL: g++.dg/tsan/fd_close_norace2.C -O2 execution test FAIL: g++.dg/tsan/fd_close_norace.C -O0 execution test FAIL: g++.dg/tsan/fd_close_norace.C -O2 execution test New passes: FAIL: 27_io/basic_istream/ignore/wchar_t/94749.cc -std=gnu++17 execution test FAIL: c-c++-common/tsan/pr65400-3.c -O0 output pattern test FAIL: c-c++-common/tsan/pr68260.c -O0 execution test FAIL: c-c++-common/tsan/pr68260.c -O2 execution test FAIL: c-c++-common/tsan/race_on_barrier2.c -O0 output pattern test FAIL: c-c++-common/tsan/race_on_barrier.c -O2 output pattern test FAIL: c-c++-common/tsan/race_on_mutex.c -O2 output pattern test FAIL: c-c++-common/tsan/simple_stack.c -O0 output pattern test FAIL: c-c++-common/tsan/thread_leak1.c -O0 output pattern test FAIL: c-c++-common/tsan/thread_leak1.c -O2 output pattern test FAIL: c-c++-common/tsan/thread_leak2.c -O2 output pattern test FAIL: c-c++-common/tsan/tiny_race.c -O2 output pattern test FAIL: c-c++-common/tsan/tls_race.c -O0 output pattern test FAIL: g++.dg/tsan/pthread_cond_clockwait.C -O0 execution test
Re: [Linaro-TCWG-CI] gcc-16-1550-g9244ea4bf556: Failure on aarch64
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 wrote:
>>
>> 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 only if
>> this is not part of a range. */
>>
>>/* The compiler might warn that idx may be
>> used uninitialized, however it will be
>> reached iff elem < table_size which means
>> that it was properly set in the loop
>> above. */
>>DIAG_PUSH_NEEDS_COMMENT;
>>DIAG_IGNORE_Os_NEEDS_COMMENT (8,
>> "-Wmaybe-uninitialized");
>>if (! is_range
>>
>> # if WIDE_CHAR_VERSION
>>&& __wmemcmp (n, &wextra[1], c1) == 0
>> # else
>>&& memcmp (n, &extra[idx + 1], c1) == 0
>> # endif
>>)
>> {
>>n += c1 - 1;
>>goto matched;
>> }
>>DIAG_POP_NEEDS_COMMENT;
>> ___
>> linaro-toolchain mailing list -- linaro-toolch...@lists.linaro.org
>> To unsubscribe send an email to linaro-toolchain-le...@lists.linaro.org
>
Regressions on master at commit r16-1599 vs commit r16-1595 on Linux/x86_64
Regressions on master at commit r16-1599 vs commit r16-1595 on Linux/x86_64 New failures: FAIL: gcc.dg/lto/save-temps c_lto_save-temps_0.o-c_lto_save-temps_0.o link, -O -flto -save-temps New passes:
