From: Jim Wilson <jimw@sifive.com>
To: Andrew Burgess <andrew.burgess@embecosm.com>
Cc: Sebastian Huber <sebastian.huber@embedded-brains.de>,
gdb-patches@sourceware.org
Subject: Re: [PATCH] gdb: Prefer RISC-V register name "s0" over "fp"
Date: Fri, 29 Jun 2018 16:48:00 -0000 [thread overview]
Message-ID: <CAFyWVabfkaK72Krd7ijTKWMtv0cGvZtd=FGoUDNtg0k2quwSqg@mail.gmail.com> (raw)
In-Reply-To: <20180629120807.GG15881@embecosm.com>
On Fri, Jun 29, 2018 at 5:08 AM, Andrew Burgess
<andrew.burgess@embecosm.com> wrote:
> This is fine with me based on GCC no generating $fp relative code by
> default. However, I think we need to get binutils fixed too, $fp _is_
> a valid register name.
I can fix the assembler.
Jim
prev parent reply other threads:[~2018-06-29 16:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-29 8:58 Sebastian Huber
2018-06-29 12:08 ` Andrew Burgess
2018-06-29 16:48 ` Jim Wilson [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='CAFyWVabfkaK72Krd7ijTKWMtv0cGvZtd=FGoUDNtg0k2quwSqg@mail.gmail.com' \
--to=jimw@sifive.com \
--cc=andrew.burgess@embecosm.com \
--cc=gdb-patches@sourceware.org \
--cc=sebastian.huber@embedded-brains.de \
/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