public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth 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 07:10:01 +0000 [thread overview] Message-ID: <bug-115232-4-SWghbCZaRJ@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 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED Assignee|unassigned at gcc dot gnu.org |rguenth at gcc dot gnu.org --- Comment #3 from Richard Biener <rguenth at gcc dot gnu.org> --- (gdb) p newc $1 = (const demangle_component &) <error reading variable: Cannot access memory at address 0x0> (gdb) p delc $2 = (const demangle_component &) <error reading variable: Cannot access memory at address 0x0> 1763 demangle_component *ndc = cplus_demangle_v3_components (new_str, 0, &np); 1764 demangle_component *ddc = cplus_demangle_v3_components (del_str, 0, &dp); 1765 bool mismatch = new_delete_mismatch_p (*ndc, *ddc); (gdb) p new_str $3 = 0x7ffff7009ea8 "_ZZN5OuterIvE6methodIvEEvvQ3cstITL0__EEN5InnernwEm" (gdb) p del_str $4 = 0x7ffff7009e70 "_ZZN5OuterIvE6methodIvEEvvQ3cstITL0__EEN5InnerdlEPv" so we cannot demangle these? But we expect no failure. It should be trivial to build in safety here, mine for that. I'll keep the PR open for the failed demangle though.
next prev parent reply other threads:[~2024-05-27 7:10 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 [this message] 2024-05-27 9:24 ` cvs-commit at gcc dot gnu.org 2024-05-27 9:25 ` cvs-commit at gcc dot gnu.org 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-SWghbCZaRJ@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).