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 3DE9C3857C51; Fri,  3 Mar 2023 18:24:55 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 3DE9C3857C51
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1677867895;
	bh=x8H196ci08yoVJPhydJbEv+tjyk+YIqhQDWL1xAHYg8=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=jFmSK9zMTuBpUSIZEjUwwgEZKB6g50YEaq/Jr4bCeK59KnPJFiPQv4zAOpbMlnSdv
	 Y639gYJ8B23O+twX/YPtVPlAwB3t3mIQ63s6NrEtnmeLRJlxQvNTQeBPS2bIebtyO2
	 nv1roA43acliI1sx/SpOHx5VrbXTnbYBq8GCD2kw=
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/108996] Proposal for adding DWARF call site information
 in GCC with -O0
Date: Fri, 03 Mar 2023 18:24:53 +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: 13.0
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: pinskia at gcc dot gnu.org
X-Bugzilla-Status: NEW
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-108996-4-A0DBxEENbm@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-108996-4@http.gcc.gnu.org/bugzilla/>
References: <bug-108996-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=3D108996

--- Comment #7 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Ulrich Weigand from comment #4)
> (In reply to Jakub Jelinek from comment #3)
> > What is done on other arches?
>=20
> That depends on the platform ABI.  On some arches, including x86/x86_64 a=
nd
> arm/aarch64, the ABI requires the generated code reloads the return buffer
> pointer into a defined register at function exit (either the same it was =
in
> on function entry, or some other ABI-defined register).  On those arches,
> GDB can at least inspect the return value at the point the function return
> happens.

aarch64 does not require that. GCC produces it yes but that is a missed
optimization, see PR 103010 which I filed against GCC for that case.=