public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ebotcazou at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug debug/48220] DW_OP_GNU_entry_value/DW_TAG_GNU_call_site_parameter vs. register window targets Date: Wed, 23 Mar 2011 17:50:00 -0000 [thread overview] Message-ID: <bug-48220-4-F531yzs6pO@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-48220-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48220 --- Comment #4 from Eric Botcazou <ebotcazou at gcc dot gnu.org> 2011-03-23 17:33:54 UTC --- > The aim of the extension is to allow correct debug info, not almost correct, > so I think defining "upon entering of the current subprogram" as anything but > before the first insn in it is wrong and would make it not possible to use > DW_OP_GNU_entry_value before the point (end of prologue or what?). Yes, end of the prologue. I was under the impression that, with your alternate scheme, the opposite situation would arise, i.e. it wouldn't be possible to use DW_OP_GNU_entry_value after the end of the prologue. Given how GDB works, this sounded far less appealing than the current scheme. Sorry if I misunderstood. > As for teaching var-tracking about save/restore on SPARC, it would be a matter > of adding probably two target hooks, one that would be run e.g. at the end of > adjust_insn and would be supposed to change it using validate_change (..., > true); in whatever way var-tracking should understand the insn. > So e.g. for save you'd add into the parallel things like: > (set (reg:P 24) (reg:P 8)) > (clobber (reg:P 8)) > and similarly for all the other param regs. Perhaps even make it explicit > what exactly is subtracted from %sp. > And the second target hook would return a different rtx for DECL_INCOMING_RTL, > with registers adjusted back. Because for -O0 if we don't do var-tracking we > probably want DECL_INCOMING_RTL to still refer to %i0 etc., even when it is > not correct before the save. I see, thanks for the explanation.
next prev parent reply other threads:[~2011-03-23 17:34 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-03-21 16:35 [Bug debug/48220] New: " jakub at gcc dot gnu.org 2011-03-21 16:56 ` [Bug debug/48220] " jakub at gcc dot gnu.org 2011-03-22 22:04 ` ebotcazou at gcc dot gnu.org 2011-03-23 17:07 ` jakub at gcc dot gnu.org 2011-03-23 17:50 ` ebotcazou at gcc dot gnu.org [this message] 2011-03-23 21:13 ` jakub at gcc dot gnu.org 2011-06-02 19:40 ` ebotcazou at gcc dot gnu.org 2011-07-11 16:02 ` [Bug debug/48220] DW_OP_GNU_entry_value/DW_TAG_GNU_call_site_parameter vs register window ebotcazou at gcc dot gnu.org 2011-07-11 16:42 ` jakub at gcc dot gnu.org 2011-07-14 21:49 ` ebotcazou at gcc dot gnu.org 2011-07-15 17:10 ` ebotcazou at gcc dot gnu.org 2011-08-04 11:52 ` 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-48220-4-F531yzs6pO@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: linkBe 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).