public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Jim Wilson <jimw@sifive.com>
To: Nelson Chu <nelson.chu@sifive.com>
Cc: Binutils <binutils@sourceware.org>, Alan Modra <amodra@gmail.com>,
	 Nick Clifton <nickc@redhat.com>,
	Kito Cheng <kito.cheng@sifive.com>,
	 Andrew Waterman <andrew@sifive.com>,
	Palmer Dabbelt <palmer@dabbelt.com>,
	 Simon Cook <simon.cook@embecosm.com>,
	Jeremy Bennett <jeremy.bennett@embecosm.com>
Subject: Re: [Integration 0/6] RISC-V: The prototype of the integration and working branches for binutils.
Date: Tue, 30 Mar 2021 16:16:12 -0700	[thread overview]
Message-ID: <CAFyWVaaAx+c4BV4xX3ZL4_d9up0uGe9mjDNEQ4NKFHc2Udnx+w@mail.gmail.com> (raw)
In-Reply-To: <1617097017-16776-1-git-send-email-nelson.chu@sifive.com>

On Tue, Mar 30, 2021 at 2:37 AM Nelson Chu <nelson.chu@sifive.com> wrote:

> RISC-V GNU binutils will have another two FSF develop branches to let
> developers can contribute their works, but these works are not ratified
> yet, so they aren't allowed to merge into mainline.  The two branches are
> integration branch and working branch.  The series of patches are the
> prototypes for these two develop branches, and they won't be applied to
> the mainline.  Please see the details in the comments of the patches,
> and feels free to share any thought and suggestion, if you are interested.
>

The series looks OK to me.  I made some minor comments, other than the Zfh
fcvt.q.h and fcvt.h.q which I think are broken and need to be fixed.

Jim

  parent reply	other threads:[~2021-03-30 23:16 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-30  9:36 Nelson Chu
2021-03-30  9:36 ` [Integration 1/6] RISC-V/extended: Add extended extension hooks when parsing architecture string Nelson Chu
2021-03-30 22:46   ` Jim Wilson
2021-03-30  9:36 ` [Integration 2/6] RISC-V/extended: Add assembler and dis-assembler hooks for extended extensions Nelson Chu
2021-03-30 22:53   ` Jim Wilson
2021-03-30  9:36 ` [Integration 3/6] RISC-V/sifive: Add sifive cache control instructions Nelson Chu
2021-03-30 22:56   ` Jim Wilson
2021-03-30  9:36 ` [Integration 4/6] RISC-V/rvv: Add rvv v0.10 instructions Nelson Chu
2021-03-30  9:36 ` [Integration 5/6] RISC-V/zfh: Add half-precision floating-point v0.1 instructions Nelson Chu
2021-03-30 23:09   ` Jim Wilson
2021-04-06  2:01     ` Nelson Chu
2021-03-30  9:36 ` [Integration 6/6] RISC-V/zfh: Support .float16 directive for assembler Nelson Chu
2021-03-30 23:14   ` Jim Wilson
2021-03-30 23:16 ` Jim Wilson [this message]
2021-04-16  2:32   ` [Integration 0/6] RISC-V: The prototype of the integration and working branches for binutils Nelson Chu
2021-04-20 19:10     ` Jim Wilson
2021-04-20 21:07       ` Mike Frysinger
2021-04-22  1:39         ` Nelson Chu
2021-04-22  1:27       ` Nelson Chu

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=CAFyWVaaAx+c4BV4xX3ZL4_d9up0uGe9mjDNEQ4NKFHc2Udnx+w@mail.gmail.com \
    --to=jimw@sifive.com \
    --cc=amodra@gmail.com \
    --cc=andrew@sifive.com \
    --cc=binutils@sourceware.org \
    --cc=jeremy.bennett@embecosm.com \
    --cc=kito.cheng@sifive.com \
    --cc=nelson.chu@sifive.com \
    --cc=nickc@redhat.com \
    --cc=palmer@dabbelt.com \
    --cc=simon.cook@embecosm.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).