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/102690] New: [12 regression] g++.dg/warn/Warray-bounds-16.C fails Date: Mon, 11 Oct 2021 20:44:02 +0000 [thread overview] Message-ID: <bug-102690-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102690 Bug ID: 102690 Summary: [12 regression] g++.dg/warn/Warray-bounds-16.C fails 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: --- Somewhere in the range 177b800f5fc861af1bf8700f050de28dd47ee1aa, r12-4288 to 338725652f84793805c55f08a7607c2f45d5512b, r12-4320 these tests started failing. For some reason git bisect isn't pointing me to the right revision, though. FAIL: g++.dg/warn/Warray-bounds-16.C -std=gnu++14 scan-tree-dump-not optimized "goto" FAIL: g++.dg/warn/Warray-bounds-16.C -std=gnu++14 (test for excess errors) FAIL: g++.dg/warn/Warray-bounds-16.C -std=gnu++17 scan-tree-dump-not optimized "goto" FAIL: g++.dg/warn/Warray-bounds-16.C -std=gnu++17 (test for excess errors) FAIL: g++.dg/warn/Warray-bounds-16.C -std=gnu++2a scan-tree-dump-not optimized "goto" FAIL: g++.dg/warn/Warray-bounds-16.C -std=gnu++2a (test for excess errors) FAIL: g++.dg/warn/Warray-bounds-16.C -std=gnu++98 scan-tree-dump-not optimized "goto" FAIL: g++.dg/warn/Warray-bounds-16.C -std=gnu++98 (test for excess errors)
next reply other threads:[~2021-10-11 20:44 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-10-11 20:44 seurer at gcc dot gnu.org [this message] 2021-10-11 21:02 ` [Bug tree-optimization/102690] " pinskia at gcc dot gnu.org 2021-10-12 6:21 ` rguenth at gcc dot gnu.org 2021-10-12 6:22 ` rguenth at gcc dot gnu.org 2021-11-09 0:56 ` seurer at gcc dot gnu.org 2021-11-09 2:30 ` msebor at gcc dot gnu.org 2021-11-09 8:25 ` [Bug testsuite/102690] [11/12 " rguenth at gcc dot gnu.org 2021-11-10 8:55 ` ebotcazou at gcc dot gnu.org 2021-11-10 9:15 ` rguenth at gcc dot gnu.org 2021-11-10 10:10 ` cvs-commit at gcc dot gnu.org 2021-11-10 10:10 ` cvs-commit at gcc dot gnu.org 2021-11-10 10:11 ` rguenth at gcc dot gnu.org 2021-11-10 11:49 ` ebotcazou at gcc dot gnu.org 2022-04-21 7:50 ` rguenth at gcc dot gnu.org 2022-06-30 2:15 ` [Bug testsuite/102690] [11/12/13 " cvs-commit at gcc dot gnu.org 2023-05-29 10:05 ` [Bug testsuite/102690] [11/12/13/14 " jakub 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-102690-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).