public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/109524] [13 Regression] ICE: SIGSEGV in remove_unreachable::remove_and_update_globals (tree-vrp.cc:136) with -O3 -fno-tree-forwprop -fnon-call-exceptions -fno-tree-ccp -fno-tree-fre Date: Wed, 19 Apr 2023 08:04:58 +0000 [thread overview] Message-ID: <bug-109524-4-kXhDOuMage@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-109524-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109524 --- Comment #12 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Jakub Jelinek <jakub@gcc.gnu.org>: https://gcc.gnu.org/g:794ffdb0fb6312ce07af0bfc797bef9f4cff4c61 commit r14-59-g794ffdb0fb6312ce07af0bfc797bef9f4cff4c61 Author: Jakub Jelinek <jakub@redhat.com> Date: Wed Apr 19 10:01:04 2023 +0200 testsuite: Fix up pr109524.C for -std=c++23 [PR109524] This testcase was reduced such that it isn't valid C++23, so with my usual testing with GXX_TESTSUITE_STDS=98,11,14,17,20,2b it fails: FAIL: g++.dg/pr109524.C -std=gnu++2b (test for excess errors) .../gcc/testsuite/g++.dg/pr109524.C: In function 'nn hh(nn)': .../gcc/testsuite/g++.dg/pr109524.C:35:12: error: cannot bind non-const lvalue reference of type 'nn&' to an rvalue of type 'nn' .../gcc/testsuite/g++.dg/pr109524.C:17:6: note: initializing argument 1 of 'nn::nn(nn&)' The following patch fixes that and I've verified it doesn't change anything on what the test was testing, it still ICEs in r13-7198 and passes in r13-7203, now in all language modes (except for 98 where it is intentionally UNSUPPORTED). 2023-04-19 Jakub Jelinek <jakub@redhat.com> PR tree-optimization/109524 * g++.dg/pr109524.C (nn::nn): Change argument type from nn & to const nn &.
next prev parent reply other threads:[~2023-04-19 8:04 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-04-15 10:27 [Bug tree-optimization/109524] New: " zsojka at seznam dot cz 2023-04-15 19:50 ` [Bug tree-optimization/109524] " pinskia at gcc dot gnu.org 2023-04-15 20:17 ` pinskia at gcc dot gnu.org 2023-04-15 20:18 ` pinskia at gcc dot gnu.org 2023-04-15 20:33 ` jakub at gcc dot gnu.org 2023-04-15 20:38 ` pinskia at gcc dot gnu.org 2023-04-15 20:55 ` jakub at gcc dot gnu.org 2023-04-15 21:12 ` pinskia at gcc dot gnu.org 2023-04-15 22:49 ` jakub at gcc dot gnu.org 2023-04-15 23:00 ` jakub at gcc dot gnu.org 2023-04-17 7:22 ` rguenth at gcc dot gnu.org 2023-04-17 9:03 ` cvs-commit at gcc dot gnu.org 2023-04-17 9:04 ` rguenth at gcc dot gnu.org 2023-04-19 8:04 ` cvs-commit at gcc dot gnu.org [this message] 2023-04-19 8:09 ` cvs-commit 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-109524-4-kXhDOuMage@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).