From: Jeff Law <law@redhat.com>
To: "Maciej W. Rozycki" <macro@wdc.com>
Cc: Jim Wilson <jimw@sifive.com>, gcc-patches@gcc.gnu.org
Subject: Re: [PING][PATCH][wwwdocs] GCC 10: Document RISC-V target's requirement for binutils 2.30
Date: Thu, 09 Apr 2020 08:40:31 -0600 [thread overview]
Message-ID: <df131a1d8a37171f09ca2948542355835927f55a.camel@redhat.com> (raw)
In-Reply-To: <alpine.LFD.2.21.2004091529590.461@redsun52.ssa.fujisawa.hgst.com>
On Thu, 2020-04-09 at 15:36 +0100, Maciej W. Rozycki wrote:
> On Thu, 9 Apr 2020, Jeff Law wrote:
>
> > > > Match GCC commit bfe78b08471f ("RISC-V: Using fmv.x.w/fmv.w.x rather
> > > > than fmv.x.s/fmv.s.x") and commit 879bc686a0aa ("doc: RISC-V: Update
> > > > binutils requirement to 2.30").
> > >
> > > Ping for:
> > >
> > > <https://gcc.gnu.org/pipermail/gcc-patches/2020-April/543144.html>
> > OK. Do we need any configure magic to detect what assembler version is being
> > used and warn/error if it's too old?
>
> I discussed this with Jim (cc-ed) who thinks there is no need for that;
> cf. <https://gcc.gnu.org/pipermail/gcc-patches/2020-March/542280.html>;.
Great thanks.
JEff
prev parent reply other threads:[~2020-04-09 14:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-02 14:50 [PATCH][wwwdocs] " Maciej W. Rozycki
2020-04-09 13:42 ` [PING][PATCH][wwwdocs] " Maciej W. Rozycki
2020-04-09 13:59 ` Jeff Law
2020-04-09 14:36 ` Maciej W. Rozycki
2020-04-09 14:40 ` Jeff Law [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=df131a1d8a37171f09ca2948542355835927f55a.camel@redhat.com \
--to=law@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jimw@sifive.com \
--cc=macro@wdc.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).