From: Pedro Alves <palves@redhat.com>
To: Jiong Wang <jiwang@tilera.com>
Cc: gdb-patches@sourceware.org, Walter Lee <walt@tilera.com>
Subject: Re: [RFC/TileGX 2/2] fix gdbserver bug for 32bit elf
Date: Tue, 26 Feb 2013 18:24:00 -0000 [thread overview]
Message-ID: <512CF131.5020105@redhat.com> (raw)
In-Reply-To: <5110E21A.2060308@tilera.com>
On 02/05/2013 10:42 AM, Jiong Wang wrote:
> for tilegx, all general registers are 64bit, while the pseudo 'pc' is 32bit under tilegx32.
>
> gdb client treat 'pc' correctly in
>
> static struct type *
> tilegx_register_type (struct gdbarch *gdbarch, int regnum)
> {
> if (regnum == TILEGX_PC_REGNUM)
> return builtin_type (gdbarch)->builtin_func_ptr;
>
>
> while gdbserver always treat it as 64bit, there
> is mismatch.
>
> gdb/ChangeLog:
> * configure.tgt: Enable gdbserver for tilegx
This bit is an unrelated change. Please split it out
into a separate patch, and post it in a new self-contained
thread, along with its own rationale.
--
Pedro Alves
prev parent reply other threads:[~2013-02-26 18:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-05 10:42 Jiong Wang
2013-02-26 18:08 ` Pedro Alves
2013-02-27 4:27 ` Jiong Wang
2013-02-27 14:06 ` Pedro Alves
2013-02-27 14:10 ` Jiong Wang
2013-02-26 18:24 ` Pedro Alves [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=512CF131.5020105@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=jiwang@tilera.com \
--cc=walt@tilera.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