From: Pedro Alves <palves@redhat.com>
To: Max Filippov <jcmvbkbc@gmail.com>, gdb-patches@sourceware.org
Cc: Maxim Grigoriev <maxim2405@gmail.com>,
Woody LaRue <larue@cadence.com>,
Marc Gauthier <marc@cadence.com>
Subject: Re: [PATCH] xtensa: fix access to the last pseudo register
Date: Wed, 27 May 2015 10:16:00 -0000 [thread overview]
Message-ID: <55659984.90103@redhat.com> (raw)
In-Reply-To: <1431904329-13965-1-git-send-email-jcmvbkbc@gmail.com>
On 05/18/2015 12:12 AM, Max Filippov wrote:
> Currently access to the last pseudo register is aliased to a1. This is
> done by little snippets in the beginning of xtensa_pseudo_register_read
> and xtensa_pseudo_register_write that used to do such aliasing for FP
> register since bdb4c075a29dd086f0868b394b488b1c94666be6, but then
> FP_ALIAS was expanded into gdbarch_num_regs (current_gdbarch) +
> gdbarch_num_pseudo_regs (current_gdbarch) (one register past the last
> pseudo register) in 304fe2552d6e0821e8fdb7575f8e7ba6607a076d, which
> then was changed to the last pseudo register in
> 94a0e877111421d300d26b858bd3a0a27078d1e8.
IIUC, the original intention was for FP to alias a1, and then through
that series of patches (part of old current_gdbarch elimination)
we ended up aliasing the wrong register. Instead of fixing the
aliasing, you're just removing it altogether. Correct?
OK.
Thanks,
Pedro Alves
next prev parent reply other threads:[~2015-05-27 10:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-17 23:12 Max Filippov
2015-05-27 2:11 ` Max Filippov
2015-05-27 10:16 ` Pedro Alves [this message]
2015-05-27 10:55 ` Max Filippov
2015-05-27 15:13 ` Marc Gauthier
2015-05-29 9:40 ` Pedro Alves
2015-05-29 10:36 ` Max Filippov
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=55659984.90103@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=jcmvbkbc@gmail.com \
--cc=larue@cadence.com \
--cc=marc@cadence.com \
--cc=maxim2405@gmail.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