From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 485803858C5E; Fri, 3 Mar 2023 08:38:04 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 485803858C5E DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1677832684; bh=sRiNnCs+8kct80FB1NgUNVy1xQ4n3VmS9g39dSBWKsM=; h=From:To:Subject:Date:In-Reply-To:References:From; b=igpKbgQh6vkONz9ImdmYmAXA8MFafBQDCHaOJ6Z75iT6sXh7DgMEHyrFqfPcWC3hf XkWyU4P5Iz+5y6FFQcol51GCY2S1NjZ36YrJWUzif+62Xp3kOwireCsHtDC+Hq/CMW 3yujur2fXNYRD1WkQ6dGIolSoh5nTchPj5azO45Q= From: "rguenth at gcc dot 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 08:37:58 +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: rguenth 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: cf_reconfirmed_on everconfirmed bug_status cc bug_severity version Message-ID: In-Reply-To: References: 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: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D108996 Richard Biener changed: What |Removed |Added ---------------------------------------------------------------------------- Last reconfirmed| |2023-03-03 Ever confirmed|0 |1 Status|UNCONFIRMED |NEW CC| |aoliva at gcc dot gnu.org, | |jakub at gcc dot gnu.org Severity|normal |enhancement Version|unknown |13.0 --- Comment #1 from Richard Biener --- It might be possible to run a reduced dataflow var-tracking at -O0 for this kind of things (the target could provide a set of interesting entry/exit parameters/registers to track). For other targets the biggest issue is when debugging the prologue code. I'm not sure how easy it would be to run var-tracking for a subset of insns/regs and how to then make use of such partial information when outputting DWARF. Alex/Jakub might have some ideas.=