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/104206] New: [12 regression] test case c-c++-common/pr72747-2.c fails in r12-6821 Date: Mon, 24 Jan 2022 15:01:05 +0000 [thread overview] Message-ID: <bug-104206-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104206 Bug ID: 104206 Summary: [12 regression] test case c-c++-common/pr72747-2.c fails in r12-6821 Product: gcc Version: 12.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:053bcc97f4a59e3f2811b8a1edf60fd733a580a0, r12-6821 make -k check-gcc RUNTESTFLAGS="dg.exp=c-c++-common/pr72747-2.c" FAIL: c-c++-common/pr72747-2.c -std=gnu++98 scan-tree-dump-times gimple " w = {i.0_1}" 1 FAIL: c-c++-common/pr72747-2.c -std=gnu++14 scan-tree-dump-times gimple " w = {i.0_1}" 1 FAIL: c-c++-common/pr72747-2.c -std=gnu++17 scan-tree-dump-times gimple " w = {i.0_1}" 1 FAIL: c-c++-common/pr72747-2.c -std=gnu++20 scan-tree-dump-times gimple " w = {i.0_1}" 1 # of expected passes 2 # of expected passes 4 # of unexpected failures 4 commit 053bcc97f4a59e3f2811b8a1edf60fd733a580a0 (HEAD, refs/bisect/bad) Author: Jason Merrill <jason@redhat.com> Date: Thu Jan 20 05:45:02 2022 -0500 c++: constexpr and -fno-elide-constructors [PR101072]
next reply other threads:[~2022-01-24 15:01 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-01-24 15:01 seurer at gcc dot gnu.org [this message] 2022-01-24 18:30 ` [Bug c++/104206] " pinskia at gcc dot gnu.org 2022-01-25 7:54 ` rguenth at gcc dot gnu.org 2022-01-26 15:55 ` jason at gcc dot gnu.org 2022-01-26 19:27 ` cvs-commit at gcc dot gnu.org 2022-01-26 19:28 ` jason 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-104206-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).