public inbox for gcc-cvs-wwwdocs@sourceware.org
help / color / mirror / Atom feed
From: "Maciej W. Rozycki" <macro@sourceware.org>
To: gcc-cvs-wwwdocs@gcc.gnu.org
Subject: gcc-wwwdocs branch master updated. cd4b2be81b0777a2221a8c5d77844910ad038e3d
Date: Thu,  9 Apr 2020 14:36:00 +0000 (GMT)	[thread overview]
Message-ID: <20200409143600.C1DAE385B835@sourceware.org> (raw)

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "gcc-wwwdocs".

The branch, master has been updated
       via  cd4b2be81b0777a2221a8c5d77844910ad038e3d (commit)
      from  12624a2d994e342ee38be548beb02c1937241041 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit cd4b2be81b0777a2221a8c5d77844910ad038e3d
Author: Maciej W. Rozycki <macro@wdc.com>
Date:   Thu Apr 9 15:35:20 2020 +0100

    GCC 10: Document RISC-V target's requirement for binutils 2.30
    
    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").

diff --git a/htdocs/gcc-10/changes.html b/htdocs/gcc-10/changes.html
index c24d1f84..1c8d7a9f 100644
--- a/htdocs/gcc-10/changes.html
+++ b/htdocs/gcc-10/changes.html
@@ -729,7 +729,13 @@ a work-in-progress.</p>
   </li>
 </ul>
 
-<!-- <h3 id="riscv">RISC-V</h3> -->
+<h3 id="riscv">RISC-V</h3>
+<ul>
+  <li>
+    The <code>riscv*-*-*</code> targets now require GNU binutils version 2.30
+    or later, to support new assembly instructions produced by GCC.
+  </li>
+</ul>
 
 <!-- <h3 id="rx">RX</h3> -->
 

-----------------------------------------------------------------------

Summary of changes:
 htdocs/gcc-10/changes.html | 8 +++++++-
 1 file changed, 7 insertions(+), 1 deletion(-)


hooks/post-receive
-- 
gcc-wwwdocs


                 reply	other threads:[~2020-04-09 14:36 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20200409143600.C1DAE385B835@sourceware.org \
    --to=macro@sourceware.org \
    --cc=gcc-cvs-wwwdocs@gcc.gnu.org \
    /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).