From: Daniel Jacobowitz <dan@codesourcery.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Pedro Alves <pedro@codesourcery.com>,
gdb-patches@sourceware.org, hjl.tools@gmail.com,
msnyder@vmware.com
Subject: Re: PATCH: Support x86 pseudo registers
Date: Fri, 12 Mar 2010 16:30:00 -0000 [thread overview]
Message-ID: <20100312162949.GA22104@caradoc.them.org> (raw)
In-Reply-To: <83iq9134rm.fsf@gnu.org>
On Fri, Mar 12, 2010 at 06:04:45PM +0200, Eli Zaretskii wrote:
> Maybe, but frankly I don't really understand what it says, exactly.
> Does it mean that if the name does clash with the architecture, the
> architecture's meaning is used?
I think that's what was intended.
> Anyway, are there any such conflicts in the current codebase?
Yeah, there are. On some platforms, "$fp" is a GDB-computed value
based on the frame unwinder. On others, it's a register that may or
may not have a frame pointer in it right now. For instance, $fp on
ARM is r11; "fp" on M68K is between a5 and sp. On i386 it's
calculated. You'll get different results for this:
(gdb) p $fp
$1 = (void *) 0x7fffffffdec0
(gdb) p $fp --
Left operand of assignment is not an lvalue.
Whaddaya mean $fp isn't an lvalue? Oh, it's an internal value, not an
alias for $rbp.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2010-03-12 16:30 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-01 17:02 H.J. Lu
2010-03-02 11:17 ` Mark Kettenis
2010-03-02 13:55 ` Daniel Jacobowitz
2010-03-02 14:08 ` H.J. Lu
2010-03-02 15:04 ` Daniel Jacobowitz
2010-03-02 15:37 ` H.J. Lu
2010-03-02 17:54 ` Eli Zaretskii
2010-03-02 19:01 ` H.J. Lu
2010-03-02 20:54 ` Eli Zaretskii
2010-03-02 21:06 ` H.J. Lu
2010-03-02 21:47 ` Eli Zaretskii
2010-03-02 21:52 ` Daniel Jacobowitz
2010-03-02 21:57 ` Michael Snyder
2010-03-02 22:00 ` H.J. Lu
2010-03-02 22:07 ` H.J. Lu
2010-03-03 17:33 ` Eli Zaretskii
2010-03-03 17:53 ` H.J. Lu
2010-03-03 18:09 ` Eli Zaretskii
2010-03-03 20:20 ` H.J. Lu
2010-03-12 4:23 ` Pedro Alves
2010-03-12 5:32 ` H.J. Lu
2010-03-12 6:07 ` H.J. Lu
2010-03-12 18:22 ` Michael Snyder
2010-03-12 8:30 ` Eli Zaretskii
2010-03-12 15:26 ` Pedro Alves
2010-03-12 16:04 ` Eli Zaretskii
2010-03-12 16:30 ` Daniel Jacobowitz [this message]
2010-03-12 18:14 ` Eli Zaretskii
2010-03-12 18:20 ` Pedro Alves
2010-03-12 18:55 ` Eli Zaretskii
2010-03-12 19:47 ` H.J. Lu
2010-03-12 16:31 ` Pedro Alves
2010-03-02 21:58 ` H.J. Lu
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=20100312162949.GA22104@caradoc.them.org \
--to=dan@codesourcery.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=hjl.tools@gmail.com \
--cc=msnyder@vmware.com \
--cc=pedro@codesourcery.com \
/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