> Take Maxim up on their offer, I think? It's possible the issue is latent
> so worth looking into nonetheless.
I see, I will ping Maxim later for this as I am in the middle of sth.
Pan
-Original Message-
From: Sam James
Sent: Wednesday, November 13, 2024 10:32 AM
To: Li, Pan2
Cc: Max
Regressions on master at commit r15-5210 vs commit r15-5204 on Linux/x86_64
New failures:
New passes:
FAIL: 30_threads/async/async.cc -std=gnu++17 execution test
Regressions on master at commit r15-5204 vs commit r15-5202 on Linux/x86_64
New failures:
FAIL: 30_threads/async/async.cc -std=gnu++17 execution test
New passes:
Regressions on master at commit r15-5202 vs commit r15-5201 on Linux/x86_64
New failures:
New passes:
FAIL: 30_threads/async/async.cc -std=gnu++17 execution test
Regressions on master at commit r15-5201 vs commit r15-5191 on Linux/x86_64
New failures:
FAIL: 30_threads/async/async.cc -std=gnu++17 execution test
New passes:
Regressions on releases/gcc-13 at commit r13-9183 vs commit r13-9173 on
Linux/x86_64
New failures:
FAIL: c-c++-common/tsan/atomic_stack.c -O0 output pattern test
FAIL: c-c++-common/tsan/atomic_stack.c -O2 output pattern test
FAIL: c-c++-common/tsan/bitfield_race.c -O0 output pattern test
