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/115232] [14/15 regression] ICE during GIMPLE pass during waccess Date: Mon, 27 May 2024 09:25:11 +0000 [thread overview] Message-ID: <bug-115232-4-dEuaOIlEV0@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-115232-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115232 --- Comment #5 from GCC Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-14 branch has been updated by Richard Biener <rguenth@gcc.gnu.org>: https://gcc.gnu.org/g:4790076933ef9337553c3fbbc52a93cce78c584f commit r14-10247-g4790076933ef9337553c3fbbc52a93cce78c584f Author: Richard Biener <rguenther@suse.de> Date: Mon May 27 09:13:11 2024 +0200 tree-optimization/115232 - demangle failure during -Waccess For the following testcase we fail to demangle _ZZN5OuterIvE6methodIvEEvvQ3cstITL0__EEN5InnernwEm and _ZZN5OuterIvE6methodIvEEvvQ3cstITL0__EEN5InnerdlEPv and in turn end up building NULL references. The following puts in a safeguard for faile demangling into -Waccess. PR tree-optimization/115232 * gimple-ssa-warn-access.cc (new_delete_mismatch_p): Handle failure to demangle gracefully. * g++.dg/pr115232.C: New testcase. (cherry picked from commit 311d7f5c17b8969c7ed8e4f23178d6ec4752e33f)
next prev parent reply other threads:[~2024-05-27 9:25 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-05-26 11:45 [Bug c++/115232] New: [14 regression] ICE during GIMPLE pass vopl at bk dot ru 2024-05-26 12:00 ` [Bug c++/115232] " pinskia at gcc dot gnu.org 2024-05-26 12:00 ` [Bug tree-optimization/115232] [14/15 regression] ICE during GIMPLE pass during waccess pinskia at gcc dot gnu.org 2024-05-26 12:01 ` pinskia at gcc dot gnu.org 2024-05-27 7:10 ` rguenth at gcc dot gnu.org 2024-05-27 9:24 ` cvs-commit at gcc dot gnu.org 2024-05-27 9:25 ` cvs-commit at gcc dot gnu.org [this message] 2024-05-27 9:25 ` rguenth at gcc dot gnu.org 2024-05-27 9:26 ` rguenth 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-115232-4-dEuaOIlEV0@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).