From: Pedro Alves <pedro@codesourcery.com>
To: gdb-patches@sourceware.org, Eli Zaretskii <eliz@gnu.org>
Cc: Daniel Jacobowitz <dan@codesourcery.com>,
hjl.tools@gmail.com, msnyder@vmware.com
Subject: Re: PATCH: Support x86 pseudo registers
Date: Fri, 12 Mar 2010 18:20:00 -0000 [thread overview]
Message-ID: <201003121820.10722.pedro@codesourcery.com> (raw)
In-Reply-To: <83d3z92ysk.fsf@gnu.org>
On Friday 12 March 2010 18:13:47, Eli Zaretskii wrote:
> > Date: Fri, 12 Mar 2010 11:30:04 -0500
> > From: Daniel Jacobowitz <dan@codesourcery.com>
> > Cc: Pedro Alves <pedro@codesourcery.com>, gdb-patches@sourceware.org,
> > hjl.tools@gmail.com, msnyder@vmware.com
> >
> > 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.
>
> Then maybe we should say when there's conflict, the generic name
> _might_ be unavailable.
>
We could also stick to defaulting to the architecture meaning, and
always provide $_pc, $_sp, $_fp, $_ps registers that always map to
the generic versions. That way, when there's a conflict,
there's always an escape route.
--
Pedro Alves
next prev parent reply other threads:[~2010-03-12 18:20 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
2010-03-12 18:14 ` Eli Zaretskii
2010-03-12 18:20 ` Pedro Alves [this message]
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=201003121820.10722.pedro@codesourcery.com \
--to=pedro@codesourcery.com \
--cc=dan@codesourcery.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=hjl.tools@gmail.com \
--cc=msnyder@vmware.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