public inbox for
help / color / mirror / Atom feed
From: Sebastian Huber <>
Subject: gcc-wwwdocs branch master updated. e4354be46ea2252b983989a5f7bff3bac6ee1963
Date: Mon, 18 Jan 2021 06:18:31 +0000 (GMT)	[thread overview]
Message-ID: <> (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  e4354be46ea2252b983989a5f7bff3bac6ee1963 (commit)
      from  4efcd4dbc9ee7358727451059bb0dbf45ba093f4 (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 e4354be46ea2252b983989a5f7bff3bac6ee1963
Author: Sebastian Huber <>
Date:   Sun Jan 17 20:07:48 2021 +0100

    Add nios2 changes for GCC 11

diff --git a/htdocs/gcc-11/changes.html b/htdocs/gcc-11/changes.html
index 3527428f..7eeffb98 100644
--- a/htdocs/gcc-11/changes.html
+++ b/htdocs/gcc-11/changes.html
@@ -409,7 +409,20 @@ a work-in-progress.</p>
 <!-- <h3 id="nds32">NDS32</h3> -->
-<!-- <h3 id="nios2">Nios II</h3> -->
+<h3 id="nios2">Nios II</h3>
+  <li>The options <code>-mcustom-insn=N</code> no longer produce compiler
+      warnings if the custom instruction is not generated due to missing
+      optimization options such as <code>-fno-math-errno</code>,
+      <code>-ffinite-math-only</code>, or
+      <code>-funsafe-math-optimizations</code>.  These warnings were not
+      consistently emitted for all custom instructions.
+  </li>
+  <li>The <code>-mcustom-fpu-cfg=fph2</code> option has been added to enable
+      the custom instructions supported by the <em>Nios II Floating Point
+      Hardware 2 Component</em>.
+  </li>
 <h3 id="nvptx">NVPTX</h3>


Summary of changes:
 htdocs/gcc-11/changes.html | 15 ++++++++++++++-
 1 file changed, 14 insertions(+), 1 deletion(-)


                 reply	other threads:[~2021-01-18  6:18 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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).