public inbox for gcc-cvs-wwwdocs@sourceware.org
help / color / mirror / Atom feed
From: gjl@gcc.gnu.org
To: gcc-cvs-wwwdocs@gcc.gnu.org
Subject: gcc-wwwdocs branch master updated. 051594a2c66870dd65129e38b845e94da65b7a0c
Date: Fri, 10 Jan 2020 12:29:00 -0000	[thread overview]
Message-ID: <20200110122932.8250.qmail@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  051594a2c66870dd65129e38b845e94da65b7a0c (commit)
       via  5333a3741911f4cbd1bc679922a665991190c61b (commit)
      from  a46c6a95e369659dc03c6052f49ff1061b37935d (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 051594a2c66870dd65129e38b845e94da65b7a0c
Merge: 5333a37 a46c6a9
Author: Georg Lay <georg.lay@hightec-rt.com>
Date:   Fri Jan 10 13:27:40 2020 +0100

    Merge branch 'master' of git+ssh://gcc.gnu.org/sourceware/projects/gcc-home/wwwdocs

diff --cc htdocs/gcc-10/changes.html
index a209087,8f49801..c68e00b
--- a/htdocs/gcc-10/changes.html
+++ b/htdocs/gcc-10/changes.html
@@@ -333,55 -392,34 +392,81 @@@ a work-in-progress.</p
    code sharing on MMU-less systems. The corresponding target triple is
    <code>arm-uclinuxfdpiceabi</code>, and the C library is uclibc-ng.
    </li>
+   <li>Support has been added for the Arm EABI on NetBSD through the
+   <code>arm*-*-netbsdelf-*eabi*</code> triplet.
+   </li>
+   <li>The handling of 64-bit integer operations has been significantly reworked
+   and improved leading to improved performance and reduced stack usage when using
+   64-bit integral data types.  The option <code>-mneon-for-64bits</code> is now
+   deprecated and will be removed in a future release.</li>
+   <li>
+        Support has been added for the following processors
+        (GCC identifiers in parentheses):
+        <ul>
+          <li>Arm Cortex-A77 (<code>cortex-a77</code>).</li>
+ 	 <li>Arm Cortex-A76AE (<code>cortex-a76ae</code>).</li>
+ 	 <li>Arm Cortex-M35P (<code>cortex-m35p</code>).</li>
+        </ul>
+        The GCC identifiers can be used
+        as arguments to the <code>-mcpu</code> or <code>-mtune</code> options,
+        for example: <code>-mcpu=cortex-a77</code> or
+        <code>-mtune=cortex-m35p</code>.
+   </li>
+   <li>Support has been extended for the ACLE
+   <a href="https://developer.arm.com/docs/101028/0009/data-processing-intrinsics">
+   data-processing intrinsics</a> to include 32-bit SIMD, saturating arithmetic,
+   16-bit multiplication and other related intrinsics aimed at DSP algorithm
+   optimization.
+    </li>
  </ul>
 -<!-- <h3 id="avr">AVR</h3> -->
 +
 +<h3 id="avr">AVR</h3>
 +<ul>
 +  <li>Support for the XMEGA-like devices
 +    <blockquote>
 +      ATtiny202, ATtiny204, ATtiny402, ATtiny404, ATtiny406, ATtiny804,
 +      ATtiny806, ATtiny807, ATtiny1604, ATtiny1606, ATtiny1607, ATmega808,
 +      ATmega809, ATmega1608, ATmega1609, ATmega3208, ATmega3209,
 +      ATmega4808, ATmega4809
 +    </blockquote>
 +    has been added.
 +  </li>
 +  <li>
 +    A new command line option <code>-nodevicespecs</code> has been added.
 +    It allows to provide a custom device-specs file by means of
 +    <blockquote><code>
 +	avr-gcc -nodevicespecs -specs=<em>my-spec-file</em> &lt;options&gt;
 +    </code></blockquote>
 +    and without the need to provide options <code>-B</code> and
 +    <code>-mmcu=</code>.
 +    See
 +    <a href="https://gcc.gnu.org/onlinedocs/gcc/AVR-Options.html#index-nodevicespecs">AVR
 +      command line options</a> for details.
 +    This feature is also available in v9.3+ and v8.4+.
 +  </li>
 +  <li>
 +    New command line options <code>-mdouble=[32,64]</code> and
 +    <code>-mlong-double=[32,64]</code> have been added.  They allow
 +    to chose the size (in bits) of the <code>double</code> and
 +    <code>long double</code> types, respectively.  Whether or not the
 +    mentioned layouts are available, whether the options act
 +    as a multilib option, and what is the default for either option
 +    is controlled by the new
 +    <a href="https://gcc.gnu.org/install/configure.html#avr">AVR configure
 +      options</a>
 +    <code>--with-double=</code> and <code>--with-long-double=</code>.
 +  </li>
 +  <li>
 +    A new configure option <code>--with-libf7=</code> has been added.
 +    It controls to which level avr-libgcc provides 64-bit floating point
 +    support by means of
 +    <a href="https://gcc.gnu.org/wiki/avr-gcc#Libf7">Libf7</a>.
 +  </li>
 +  <li>
 +    A new configure option <code>--with-double-comparison=</code> has been
 +    added. It's unlikely you need to set this option by hand.
 +  </li>
 +</ul>
  
  <!-- <h3 id="hsa">Heterogeneous Systems Architecture</h3> -->
  

commit 5333a3741911f4cbd1bc679922a665991190c61b
Author: Georg Lay <georg.lay@hightec-rt.com>
Date:   Fri Jan 10 13:27:31 2020 +0100

    Add AVR news.

diff --git a/htdocs/gcc-10/changes.html b/htdocs/gcc-10/changes.html
index d610826..a209087 100644
--- a/htdocs/gcc-10/changes.html
+++ b/htdocs/gcc-10/changes.html
@@ -334,7 +334,54 @@ a work-in-progress.</p>
   <code>arm-uclinuxfdpiceabi</code>, and the C library is uclibc-ng.
   </li>
 </ul>
-<!-- <h3 id="avr">AVR</h3> -->
+
+<h3 id="avr">AVR</h3>
+<ul>
+  <li>Support for the XMEGA-like devices
+    <blockquote>
+      ATtiny202, ATtiny204, ATtiny402, ATtiny404, ATtiny406, ATtiny804,
+      ATtiny806, ATtiny807, ATtiny1604, ATtiny1606, ATtiny1607, ATmega808,
+      ATmega809, ATmega1608, ATmega1609, ATmega3208, ATmega3209,
+      ATmega4808, ATmega4809
+    </blockquote>
+    has been added.
+  </li>
+  <li>
+    A new command line option <code>-nodevicespecs</code> has been added.
+    It allows to provide a custom device-specs file by means of
+    <blockquote><code>
+	avr-gcc -nodevicespecs -specs=<em>my-spec-file</em> &lt;options&gt;
+    </code></blockquote>
+    and without the need to provide options <code>-B</code> and
+    <code>-mmcu=</code>.
+    See
+    <a href="https://gcc.gnu.org/onlinedocs/gcc/AVR-Options.html#index-nodevicespecs">AVR
+      command line options</a> for details.
+    This feature is also available in v9.3+ and v8.4+.
+  </li>
+  <li>
+    New command line options <code>-mdouble=[32,64]</code> and
+    <code>-mlong-double=[32,64]</code> have been added.  They allow
+    to chose the size (in bits) of the <code>double</code> and
+    <code>long double</code> types, respectively.  Whether or not the
+    mentioned layouts are available, whether the options act
+    as a multilib option, and what is the default for either option
+    is controlled by the new
+    <a href="https://gcc.gnu.org/install/configure.html#avr">AVR configure
+      options</a>
+    <code>--with-double=</code> and <code>--with-long-double=</code>.
+  </li>
+  <li>
+    A new configure option <code>--with-libf7=</code> has been added.
+    It controls to which level avr-libgcc provides 64-bit floating point
+    support by means of
+    <a href="https://gcc.gnu.org/wiki/avr-gcc#Libf7">Libf7</a>.
+  </li>
+  <li>
+    A new configure option <code>--with-double-comparison=</code> has been
+    added. It's unlikely you need to set this option by hand.
+  </li>
+</ul>
 
 <!-- <h3 id="hsa">Heterogeneous Systems Architecture</h3> -->
 

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

Summary of changes:
 htdocs/gcc-10/changes.html |   49 +++++++++++++++++++++++++++++++++++++++++++-
 1 files changed, 48 insertions(+), 1 deletions(-)


hooks/post-receive
-- 
gcc-wwwdocs


                 reply	other threads:[~2020-01-10 12:29 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=20200110122932.8250.qmail@sourceware.org \
    --to=gjl@gcc.gnu.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).