From: "H.J. Lu" <hjl.tools@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>, "H.J. Lu" <hjl.tools@gmail.com>,
gdb-patches@sourceware.org
Subject: Re: PATCH: Support x86 pseudo registers
Date: Tue, 02 Mar 2010 21:58:00 -0000 [thread overview]
Message-ID: <6dc9ffc81003021358m7db842bcrdac32563a3b46192@mail.gmail.com> (raw)
In-Reply-To: <20100302215235.GA3894@caradoc.them.org>
On Tue, Mar 2, 2010 at 1:52 PM, Daniel Jacobowitz <dan@codesourcery.com> wrote:
> On Tue, Mar 02, 2010 at 11:47:35PM +0200, Eli Zaretskii wrote:
>> Who can help out here? I can help with wording, if someone tells the
>> story.
>
> Presumably H. J. knows why he wrote the patch?
>
> I presume it lets us say $ah or $ax in addition to $eax, and lets $eax
> work on 64-bit systems where we really have $rax.
>
Exactly. I can do
(top-gdb) disass
Dump of assembler code for function main:
0x000000000044ce70 <+0>: sub $0x28,%rsp
0x000000000044ce74 <+4>: movq $0x0,(%rsp)
0x000000000044ce7c <+12>: mov %edi,(%rsp)
=> 0x000000000044ce7f <+15>: mov %rsp,%rdi
0x000000000044ce82 <+18>: movq $0x0,0x10(%rsp)
0x000000000044ce8b <+27>: mov %rsi,0x8(%rsp)
0x000000000044ce90 <+32>: movq $0x6a6ed0,0x18(%rsp)
0x000000000044ce99 <+41>: callq 0x44ceb0 <gdb_main>
0x000000000044ce9e <+46>: add $0x28,%rsp
0x000000000044cea2 <+50>: retq
End of assembler dump.
(top-gdb) p/x $edi
$1 = 0x1
(top-gdb) p/x $rdi
$2 = 0x1
(top-gdb)
--
H.J.
prev parent reply other threads:[~2010-03-02 21:58 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
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 [this message]
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=6dc9ffc81003021358m7db842bcrdac32563a3b46192@mail.gmail.com \
--to=hjl.tools@gmail.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.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