public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Nelson Chu <nelson@rivosinc.com>
To: Jeff Law <jeffreyalaw@gmail.com>
Cc: binutils@sourceware.org
Subject: Re: [PATCH v3 0/2] RISC-V psABI: Assign DWARF register numbers to vector registers
Date: Mon, 3 Oct 2022 09:36:21 +0800	[thread overview]
Message-ID: <CAPpQWtA0KHRfXBERaP9mLwE44WSoDH4YVyCau76zZaRCDz_Osg@mail.gmail.com> (raw)
In-Reply-To: <7cea93e7-f75b-2d5a-d63b-73288d4b3e5e@gmail.com>

On Sun, Oct 2, 2022 at 11:59 PM Jeff Law via Binutils
<binutils@sourceware.org> wrote:
>
> On 10/1/22 14:27, Andrew Burgess via Binutils wrote:
> > I can't approve binutils patches, but as this mentioned RISC-V and
> > DWARF, both of which I'm interested in, I took a look :)
> >
> > Both these patches look good to me.  The register numbers align with the
> > spec, and the test makes sense.
>
> Well, that's the key property -- they align with the spec.
>
>
> I'm also not sure if I can approve for binutils, but if I can, OK for
> the trunk ;-)

Thanks for your help, Andrew and Jeff!

Hi Jeff,

Of course!  You are a global maintainer of both gcc and binutils.
Welcome and please feel free to approve any RISC-V binutils patch if
you are free and the patch looks good to you :-)

Thanks!
Nelson

  parent reply	other threads:[~2022-10-03  1:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-22  6:32 Tsukasa OI
2022-09-22  6:32 ` [PATCH v3 1/2] RISC-V: Assign DWARF " Tsukasa OI
2022-09-22  6:32 ` [PATCH v3 2/2] RISC-V: Add testcase for DWARF register numbers Tsukasa OI
2022-10-01 20:27 ` [PATCH v3 0/2] RISC-V psABI: Assign DWARF register numbers to vector registers Andrew Burgess
2022-10-02 15:58   ` Jeff Law
2022-10-02 19:35     ` Palmer Dabbelt
2022-10-03  1:36     ` Nelson Chu [this message]
2022-10-03  4:04       ` Jeff Law
2022-10-03  4:31       ` Tsukasa OI

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=CAPpQWtA0KHRfXBERaP9mLwE44WSoDH4YVyCau76zZaRCDz_Osg@mail.gmail.com \
    --to=nelson@rivosinc.com \
    --cc=binutils@sourceware.org \
    --cc=jeffreyalaw@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).