From: Yao Qi <qiyaoltc@gmail.com>
To: Pedro Alves <palves@redhat.com>
Cc: Andrew Pinski <apinski@cavium.com>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
binutils@sourceware.org
Subject: Re: [PATCH 3/3] Handle ILP32 AARCH64 correctly for gdbserver
Date: Wed, 31 Aug 2016 12:58:00 -0000 [thread overview]
Message-ID: <CAH=s-PO_X=OUdzc6hs8Hq6fBe2+ux+J6Y6rG4=5Z7jKtM9TSxg@mail.gmail.com> (raw)
In-Reply-To: <f50087f8-095e-7d4f-e965-b3a44cc4412a@redhat.com>
On Wed, Aug 31, 2016 at 11:42 AM, Pedro Alves <palves@redhat.com> wrote:
> On 08/30/2016 01:25 AM, Andrew Pinski wrote:
>> In gdbserver, we need to send over 32bit registers
>> for pc/sp instead of 64bit as we do right now.
>> So we need another XML file for ILP32.
>
> Why do we need to do that? The raw, architecture register
> is still 64-bit, right?
>
I want to ask the same... ILP32 is an ABI, it shouldn't affect the
review to architecture register.
> Sounds to me that if you want to present a 32-bit pc to the user, then
> gdb should handle this, via a pseudo register, similarly to how
> x32 sends 64-bit rip, and then gdb shows a 32-bit pc. Mips does
> something like this too, to a larger extent, see mips_register_name.
>
Why do we need to present a 32-bit pc to the user? It is 64-bit, and
I expect a 64-bit value is shown.
--
Yao (齐尧)
next prev parent reply other threads:[~2016-08-31 12:58 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-30 0:26 [PATCH 0/3] Support AARCH64 ILP32 for gdb Andrew Pinski
2016-08-30 0:26 ` [PATCH 1/3] Move AARCH64 ILP32 rejection handling Andrew Pinski
2016-08-30 0:26 ` [PATCH 3/3] Handle ILP32 AARCH64 correctly for gdbserver Andrew Pinski
2016-08-30 8:01 ` Andreas Schwab
2016-08-31 10:42 ` Pedro Alves
2016-08-31 12:58 ` Yao Qi [this message]
2016-08-31 20:02 ` Andrew Pinski
2016-08-30 0:26 ` [PATCH 2/3] Add ILP32 support to gdb Andrew Pinski
2016-08-30 7:44 ` Andreas Schwab
2016-09-01 4:21 ` Andrew Pinski
2016-09-01 7:41 ` Andreas Schwab
2016-09-01 7:37 ` [PATCH v2 0/3] Support AARCH64 ILP32 for gdb Andrew Pinski
2016-09-01 7:36 ` [PATCH 2/3] Add ILP32 support to gdb Andrew Pinski
2016-09-01 9:50 ` Andreas Schwab
2016-09-01 13:13 ` Yao Qi
2016-09-01 7:37 ` [PATCH 1/3] Move AARCH64 ILP32 rejection handling Andrew Pinski
2016-09-01 9:43 ` Richard Earnshaw (lists)
2016-09-01 7:37 ` [PATCH 3/3] Handle ILP32 AARCH64 correctly for gdbserver Andrew Pinski
2016-09-01 8:32 ` Andreas Schwab
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='CAH=s-PO_X=OUdzc6hs8Hq6fBe2+ux+J6Y6rG4=5Z7jKtM9TSxg@mail.gmail.com' \
--to=qiyaoltc@gmail.com \
--cc=apinski@cavium.com \
--cc=binutils@sourceware.org \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).