public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub 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 21:13:00 -0000 [thread overview]
Message-ID: <bug-48220-4-FKgAJIrQW6@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 #5 from Jakub Jelinek <jakub at gcc dot gnu.org> 2011-03-23 20:30:53 UTC ---
(In reply to comment #4)
> 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.
If say reference to first parameter's original value is
DW_OP_GNU_entry_value 1 <DW_OP_reg8> (i.e. %o0), then it will work just fine
anywhere in the function. The debugger either looks up matching entry
for %o0 in DW_TAG_GNU_call_site, or a debugger could put a breakpoint on the
first insn in a function and remember the %o0 value there, then just use the
remembered value anywhere where DW_OP_GNU_entry_value appears.
And for SPARC, using %o0 is also much easier for the debugger, it doesn't have
to translate anything.
On IA-64 things are different because there it is mainly the call insn which
moves the register window, not some insn executed somewhere in function's
prologue.
next prev parent reply other threads:[~2011-03-23 20:31 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
2011-03-23 21:13 ` jakub at gcc dot gnu.org [this message]
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-FKgAJIrQW6@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).