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 AE8683858436; Wed,  2 Nov 2022 22:13:30 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org AE8683858436
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1667427210;
	bh=WrvpaJw5/wjSgRG1qF62TSXgA2ErNiMI7wOm8wuK9Kg=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=tSaH452e1rYJfUszFaGcM5CXqZjvGmXzaNG/Txxfp+VZt8nZdKFcHfRXVbPFQx0lo
	 k1C7CVhu3N+Vre8Dj2FBSbvohU7e5GG9F7HqQT5lRSQFosV0HOZirpLNpVRLZ5BbOV
	 r0mHDHQgpaYE+bVRmaRu4XORsaBb6fApMI9UpTUA=
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/107513] [Feature Request] Implement
 __attribute__((__nodebug__))
Date: Wed, 02 Nov 2022 22:13:29 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-107513-4-95gTUe6rCo@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-107513-4@http.gcc.gnu.org/bugzilla/>
References: <bug-107513-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=3D107513

--- Comment #4 from Jonathan Wakely <redi at gcc dot gnu.org> ---
But what does DW_AT_artificial do? Does gdb just ignore it? I've never noti=
ced
it helping at all.=