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
Date: Mon, 11 Jul 2011 16:02:00 -0000 [thread overview]
Message-ID: <bug-48220-4-RzGs3BeRP5@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
Eric Botcazou <ebotcazou at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Attachment #23739|0 |1
is obsolete| |
--- Comment #7 from Eric Botcazou <ebotcazou at gcc dot gnu.org> 2011-07-11 16:02:28 UTC ---
Created attachment 24740
--> http://gcc.gnu.org/bugzilla/attachment.cgi?id=24740
Tentative patch for SPARC
This appears to do the trick for the SPARC. In particular:
(gdb) run
Starting program: /nile.build/botcazou/gcc-head/sparc-sun-solaris2.8/pr48220
Breakpoint 1, fn2 (a=1, b=2, c=1) at pr48220.c:13
13 {
(gdb) disass
Dump of assembler code for function fn2:
=> 0x000106cc <+0>: save %sp, -96, %sp
0x000106d0 <+4>: clr %i0
0x000106d4 <+8>: mov 5, %o0
0x000106d8 <+12>: mov 6, %o1
0x000106dc <+16>: call 0x106c4 <fn1>
0x000106e0 <+20>: mov 7, %o2
0x000106e4 <+24>: rett %i7 + 8
0x000106e8 <+28>: nop
End of assembler dump.
(gdb) p a
$1 = 1
(gdb) p &a
Address requested for identifier "a" which is in register $o0
(gdb) nexti
17 }
(gdb) p a
$2 = 1
(gdb) p &a
Address requested for identifier "a" which is in register $i0
(gdb) nexti
15 fn1 (5, 6, 7);
(gdb) p a
$3 = <optimized out>
and the location is DW_OP_GNU_entry_value pointing to $o0 from there on.
Jakub, what do you think?
next prev parent reply other threads:[~2011-07-11 16:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-21 16:35 [Bug debug/48220] New: DW_OP_GNU_entry_value/DW_TAG_GNU_call_site_parameter vs. register window targets 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
2011-06-02 19:40 ` ebotcazou at gcc dot gnu.org
2011-07-11 16:02 ` ebotcazou at gcc dot gnu.org [this message]
2011-07-11 16:42 ` [Bug debug/48220] DW_OP_GNU_entry_value/DW_TAG_GNU_call_site_parameter vs register window 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-RzGs3BeRP5@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).