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 c++/110295] [11/12 Regression] ICE in dwarf2out_finish with local class with inherited operator delete in a templated function and -g Date: Mon, 27 Nov 2023 11:34:52 +0000 [thread overview] Message-ID: <bug-110295-4-Nfp3jS9WUd@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-110295-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110295 --- Comment #8 from GCC Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-12 branch has been updated by Richard Biener <rguenth@gcc.gnu.org>: https://gcc.gnu.org/g:60575ee7b016b4d45af3d25d0b8b239ac0fd0e0c commit r12-10006-g60575ee7b016b4d45af3d25d0b8b239ac0fd0e0c Author: Richard Biener <rguenther@suse.de> Date: Mon Jun 19 09:23:16 2023 +0200 debug/110295 - mixed up early/late debug for member DIEs When we process a scope typedef during early debug creation and we have already created a DIE for the type when the decl is TYPE_DECL_IS_STUB and this DIE is still in limbo we end up just re-parenting that type DIE instead of properly creating a DIE for the decl, eventually picking up the now completed type and creating DIEs for the members. Instead this is currently defered to the second time we come here, when we annotate the DIEs with locations late where now the type DIE is no longer in limbo and we fall through doing the job for the decl. The following makes sure we perform the necessary early tasks for this by continuing with the decl DIE creation after setting a parent for the limbo type DIE. PR debug/110295 * dwarf2out.cc (process_scope_var): Continue processing the decl after setting a parent in case the existing DIE was in limbo. * g++.dg/debug/pr110295.C: New testcase. (cherry picked from commit 963f87f8a65ec82f503ac4334a3da83b0a8a43b2)
next prev parent reply other threads:[~2023-11-27 11:34 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-06-17 8:04 [Bug c++/110295] New: internal compiler error: in dwarf2out_finish duz@sol-3.de 2023-06-17 18:49 ` [Bug c++/110295] " pinskia at gcc dot gnu.org 2023-06-17 19:05 ` [Bug c++/110295] [10/11/12/13/14 Regression] ICE in dwarf2out_finish with local class with inherited operator delete in a templated function and -g pinskia at gcc dot gnu.org 2023-06-19 7:21 ` rguenth at gcc dot gnu.org 2023-06-20 7:02 ` cvs-commit at gcc dot gnu.org 2023-06-20 7:02 ` [Bug c++/110295] [10/11/12/13 " rguenth at gcc dot gnu.org 2023-06-23 10:30 ` cvs-commit at gcc dot gnu.org 2023-07-07 10:45 ` [Bug c++/110295] [11/12 " rguenth at gcc dot gnu.org 2023-11-27 11:34 ` cvs-commit at gcc dot gnu.org [this message] 2023-12-15 12:18 ` [Bug c++/110295] [11 " cvs-commit at gcc dot gnu.org 2023-12-15 12:20 ` 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-110295-4-Nfp3jS9WUd@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).