public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "seurer at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug testsuite/96276] New: new test case c-c++-common/pr95237-6.c fails Date: Wed, 22 Jul 2020 03:19:28 +0000 [thread overview] Message-ID: <bug-96276-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96276 Bug ID: 96276 Summary: new test case c-c++-common/pr95237-6.c fails Product: gcc Version: 11.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: testsuite Assignee: unassigned at gcc dot gnu.org Reporter: seurer at gcc dot gnu.org Target Milestone: --- g:0a9d711df36b42b6494b73a90c7ebf050e904493, r11-2259 make -k check-gcc RUNTESTFLAGS=dg.exp=c-c++-common/pr95237-6.c FAIL: c-c++-common/pr95237-6.c -Wc++-compat execution test FAIL: c-c++-common/pr95237-6.c -std=gnu++98 execution test FAIL: c-c++-common/pr95237-6.c -std=gnu++14 execution test FAIL: c-c++-common/pr95237-6.c -std=gnu++17 execution test FAIL: c-c++-common/pr95237-6.c -std=gnu++2a execution test # of expected passes 1 # of expected passes 4 # of unexpected failures 1 # of unexpected failures 4 Trying one of them in gdb I see: (gdb) run Starting program: /home/seurer/gcc/git/build/gcc-test/./pr95237-6.exe Program received signal SIGABRT, Aborted. 0x00003fffb7cd258c in __GI_raise (sig=<optimized out>) at ../nptl/sysdeps/unix/sysv/linux/raise.c:55 55 return INLINE_SYSCALL (tgkill, 3, pid, selftid, sig); (gdb) where #0 0x00003fffb7cd258c in __GI_raise (sig=<optimized out>) at ../nptl/sysdeps/unix/sysv/linux/raise.c:55 #1 0x00003fffb7cd4778 in __GI_abort () at abort.c:90 #2 0x000000001000066c in main () at /home/seurer/gcc/git/gcc-test/gcc/testsuite/c-c++-common/pr95237-6.c:22
next reply other threads:[~2020-07-22 3:19 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-07-22 3:19 seurer at gcc dot gnu.org [this message] 2021-08-31 5:26 ` [Bug testsuite/96276] " pinskia at gcc dot gnu.org
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=bug-96276-4@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /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).