public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth 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 08:37:58 +0000 [thread overview]
Message-ID: <bug-108996-4-toLWNO5e7n@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108996-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108996
Richard Biener <rguenth at gcc dot gnu.org> 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 <rguenth at gcc dot gnu.org> ---
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.
next prev parent reply other threads:[~2023-03-03 8:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-02 20:28 [Bug c/108996] New: Proposal for adding DWARF call site information got " cel at us dot ibm.com
2023-03-03 8:37 ` rguenth at gcc dot gnu.org [this message]
2023-03-03 9:20 ` [Bug debug/108996] Proposal for adding DWARF call site information in " jakub at gcc dot gnu.org
2023-03-03 9:24 ` jakub at gcc dot gnu.org
2023-03-03 13:14 ` uweigand at gcc dot gnu.org
2023-03-03 13:51 ` jakub at gcc dot gnu.org
2023-03-03 15:39 ` mark at gcc dot gnu.org
2023-03-03 18:24 ` pinskia at gcc dot gnu.org
2023-03-07 8:46 ` uweigand at gcc dot gnu.org
2023-03-07 8:49 ` uweigand at gcc dot gnu.org
2023-03-07 8:53 ` jakub at gcc dot gnu.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-108996-4-toLWNO5e7n@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).