public inbox for gcc-regression@sourceware.org help / color / mirror / Atom feed
From: haochenj@shgcc100.sh.intel.com To: <gcc-regression@gcc.gnu.org>,<haochen.jiang@intel.com> Subject: Regressions on master at commit r14-10123 vs commit r14-10120 on Linux/x86_64 Date: Fri, 26 Apr 2024 04:51:19 +0800 [thread overview] Message-ID: <20240425205119.C4ABD360763@shgcc100.sh.intel.com> (raw) Regressions on master at commit r14-10123 vs commit r14-10120 on Linux/x86_64 New failures: FAIL: c-c++-common/tsan/atomic_stack.c -O0 output pattern test FAIL: c-c++-common/tsan/bitfield_race.c -O0 output pattern test FAIL: c-c++-common/tsan/fd_pipe_race.c -O0 output pattern test FAIL: c-c++-common/tsan/fd_pipe_race.c -O2 output pattern test 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/free_race.c -O0 output pattern test FAIL: c-c++-common/tsan/free_race.c -O2 output pattern test FAIL: c-c++-common/tsan/mutexset1.c -O0 output pattern test FAIL: c-c++-common/tsan/pr65400-1.c -O0 output pattern test FAIL: c-c++-common/tsan/pr65400-3.c -O0 output pattern test FAIL: c-c++-common/tsan/pr65400-3.c -O2 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 -O0 output pattern test FAIL: c-c++-common/tsan/tiny_race.c -O0 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: c-c++-common/tsan/tls_race.c -O2 output pattern test FAIL: c-c++-common/tsan/write_in_reader_lock.c -O0 output pattern test FAIL: c-c++-common/tsan/write_in_reader_lock.c -O2 output pattern test New passes: 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_barrier.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_mutex2.c -O0 output pattern test FAIL: c-c++-common/tsan/race_on_mutex2.c -O2 output pattern test FAIL: c-c++-common/tsan/race_on_mutex.c -O2 output pattern test FAIL: c-c++-common/tsan/simple_race.c -O0 output pattern test FAIL: c-c++-common/tsan/simple_race.c -O2 output pattern test FAIL: c-c++-common/tsan/simple_stack.c -O0 output pattern test FAIL: g++.dg/tsan/pthread_cond_clockwait.C -O0 execution test
reply other threads:[~2024-04-25 20:51 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20240425205119.C4ABD360763@shgcc100.sh.intel.com \ --to=haochenj@shgcc100.sh.intel.com \ --cc=gcc-regression@gcc.gnu.org \ --cc=haochen.jiang@intel.com \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).