public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/39436] g++ does not emit DW_TAG_try_block or DW_TAG_catch_block
Date: Tue, 09 Apr 2024 02:19:57 +0000 [thread overview]
Message-ID: <bug-39436-4-3R139VSKyH@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-39436-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=39436
--- Comment #7 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Andrew Pinski from comment #6)
> (In reply to Andrew Pinski from comment #5)
> > for try blocks, I do need the catch blocks so do it as the siblings.
> > For catch blocks, the child will be type that is being caught as a
> > DW_TAG_formal_parameter/DW_TAG_unspecified_parameters .
>
> Note DW_TAG_unspecified_parameters is for the catch(...) case.
>
> I am adding this more for my usage when I am coding this up to make sure I
> understand how this works.
for the VAR_DECL of the catch, I think I should be able to use
gen_formal_parameter_die.
This means the block structure will need to grow since I need another tree
here. Or maybe not. Since there seems like there are 2 BLOCKs here for the
catch.
next prev parent reply other threads:[~2024-04-09 2:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-39436-4@http.gcc.gnu.org/bugzilla/>
2024-04-09 1:43 ` pinskia at gcc dot gnu.org
2024-04-09 1:43 ` pinskia at gcc dot gnu.org
2024-04-09 1:49 ` pinskia at gcc dot gnu.org
2024-04-09 1:53 ` pinskia at gcc dot gnu.org
2024-04-09 2:00 ` pinskia at gcc dot gnu.org
2024-04-09 2:05 ` pinskia at gcc dot gnu.org
2024-04-09 2:19 ` pinskia at gcc dot gnu.org [this message]
2009-03-11 17:45 [Bug debug/39436] New: " tromey at gcc dot gnu dot org
2009-03-11 21:08 ` [Bug debug/39436] " rguenth at gcc dot gnu dot 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-39436-4-3R139VSKyH@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: link
Be 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).