From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugzilla@gcc.gnu.org>
Received: by sourceware.org (Postfix, from userid 48)
	id 01075385840B; Tue,  9 Apr 2024 02:19:57 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 01075385840B
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1712629198;
	bh=4+7XRyHJLnK6+KSmK4loE5uFPWtHQ1IRbA16AQlUNVg=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=XEZ/tu86ObifrYh8oho9FwwFzLXH0ov0GSPWxpEnFa7J/NB0GsSPsTTVYnMG9yiIC
	 r1Xp30Eelhx3Dwm1ILd/ckwvitZspVaq0+Uv7oWYsNSflVLpJySsn+zzJmWZTDIa5k
	 2fqLpAKi4GsA/JRAHDkUiCmifVfW8LPfmEP6Xo+w=
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
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: debug
X-Bugzilla-Version: 4.4.0
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: pinskia at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: pinskia at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-39436-4-3R139VSKyH@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-39436-4@http.gcc.gnu.org/bugzilla/>
References: <bug-39436-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
List-Id: <gcc-bugs.sourceware.org>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D39436

--- 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 .
>=20
> Note DW_TAG_unspecified_parameters is for the catch(...) case.
>=20
> 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.=