public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Richard Earnshaw (lists)" <Richard.Earnshaw@arm.com>
To: gcc-patches <gcc-patches@gcc.gnu.org>
Subject: [arm] Mention -mfpu=auto in release notes
Date: Tue, 20 Jun 2017 10:18:00 -0000	[thread overview]
Message-ID: <67140858-fb1f-8744-67ee-556db8e5a61b@arm.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 127 bytes --]

This patch updates the release notes to mention that -mfpu=auto has been
added and that it is now the default.

Committed.

R.

[-- Attachment #2: wwwdoc.patch --]
[-- Type: text/x-patch, Size: 1310 bytes --]

? htdocs/backends.html~
? htdocs/index.html.~1.866.~
? htdocs/readings.html.~1.261.~
? htdocs/svn.html.~1.183.~
? htdocs/svn.html~
Index: htdocs/gcc-8/changes.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-8/changes.html,v
retrieving revision 1.4
diff -u -p -r1.4 changes.html
--- htdocs/gcc-8/changes.html	4 May 2017 14:35:22 -0000	1.4
+++ htdocs/gcc-8/changes.html	20 Jun 2017 10:17:54 -0000
@@ -82,7 +82,18 @@ a work-in-progress.</h2>
 
 <h3 id="arm">ARM</h3>
 <ul>
-  <li></li>
+  <li>
+    The <code>-mfpu</code> option now takes a new option setting of
+    <code>-mfpu=auto</code>.  When set to this the floating-point and SIMD
+    settings are derived from the settings of the <code>-mcpu</code>
+    or <code>-march</code> options.  The internal CPU configurations have been
+    updated with information about the permitted floating-point configurations
+    supported.  See the user guide for further information about the extended
+    option syntax for controlling architectural extensions via the
+    <code>-march</code> option.  <code>-mfpu=auto</code> is now the default
+    setting unless the compiler has been configured with an explicit
+    <code>--with-fpu</code> option.
+  </li>
 </ul>
 
 <!-- <h3 id="avr">AVR</h3> -->

                 reply	other threads:[~2017-06-20 10: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:
  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=67140858-fb1f-8744-67ee-556db8e5a61b@arm.com \
    --to=richard.earnshaw@arm.com \
    --cc=gcc-patches@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).