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 1a5cabedd21e45515a304dece6a4706fe0d3e6cf (commit)
from adc37ed2132bb3a704919f8919ecf56a53042726 (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 1a5cabedd21e45515a304dece6a4706fe0d3e6cf
Author: Georg-Johann Lay <a...@gjlay.de>
Date: Fri Feb 28 14:38:07 2025 +0100
gcc-5/changes: Move all AVR news to #avr.
diff --git a/htdocs/gcc-5/changes.html b/htdocs/gcc-5/changes.html
index 81ad4be3..5035ed3c 100644
--- a/htdocs/gcc-5/changes.html
+++ b/htdocs/gcc-5/changes.html
@@ -33,14 +33,6 @@
<code>is_trivially_default_constructible</code>,
<code>is_trivially_copy_constructible</code> and
<code>is_trivially_copy_assignable</code> should be used instead.</li>
- <li>On AVR, support has been added for the devices ATtiny4/5/9/10/20/40.
- This requires Binutils 2.25 or newer.</li>
- <li>The AVR port uses a new scheme to describe supported devices:
- For each supported device the compiler provides a device-specific
- <a href="https://gcc.gnu.org/onlinedocs/gcc/Spec-Files.html";>spec
file</a>.
- If the compiler is used together with AVR-LibC, this requires at
- least GCC 5.2 and a version of AVR-LibC which implements
- <a href="https://savannah.nongnu.org/bugs/?44574";>feature
#44574</a>.</li>
</ul>
<h2 id="general">General Optimizer Improvements</h2>
@@ -728,31 +720,41 @@ here</a>.</p>
<h3 id="avr">AVR</h3>
<ul>
- <li>The compiler no more supports individual devices like
<code>ATmega8</code>.
+ <li>Support has been added for the devices ATtiny4/5/9/10/20/40.
+ This requires Binutils 2.25 or newer.</li>
+ <li>The port uses a new scheme to describe supported devices:
+ For each supported device, the compiler provides a device-specific
+ <a href="https://gcc.gnu.org/onlinedocs/gcc/Spec-Files.html";>spec file</a>.
+ If the compiler is used together with AVR-LibC, this requires at
+ least GCC 5.2 and a version of AVR-LibC which implements
+ <a href="https://savannah.nongnu.org/bugs/?44574";>feature #44574</a>.
+ <br/><br/>
+ As a consequence, the compiler no more supports individual devices
+ like ATmega8.
Specifying, say, <code>-mmcu=atmega8</code> triggers the usage of the
device-specific
<a href="https://gcc.gnu.org/onlinedocs/gcc/Spec-Files.html";>spec file</a>
<code>specs-atmega8</code> which is part of the installation and describes
options for the sub-processes like compiler proper, assembler and linker.
You can add support for a new device <code>-mmcu=<i>mydevice</i></code> as
follows:
- <ol>
- <li>In an empty directory <code>/<i>someplace</i></code>, create a
new
- directory <code>device-specs</code>.</li>
- <li>Copy a device spec file from the installed
<code>device-specs</code>
- folder, follow the comments in that file and then save it as
-
<code>/<i>someplace</i>/device-specs/specs-<i>mydevice</i></code>.</li>
- <li>Add <code>-B /<i>someplace</i> -mmcu=<i>mydevice</i></code> to
the
- compiler's command-line options. Notice that
<code>/<i>someplace</i></code>
- must specify an absolute path and that
<code><i>mydevice</i></code> must
- not start with "<code>avr</code>".</li>
- <li>Provided you have a device-specific library
- <code>lib<i>mydevice</i>.a</code> available, you can put it at
- <code>/<i>someplace</i></code>, dito for a device-specific startup
- file <code>crt<i>mydevice</i>.o</code>.</li>
- </ol>
- The contents of the device spec files depend on the compiler's
- configuration, in particular on <code>--with-avrlibc=no</code> and
- whether or not it is configured for RTEMS.
+ <ol>
+ <li>In an empty directory <code>/<i>someplace</i></code>, create a new
+ directory <code>device-specs</code>.</li>
+ <li>Copy a device spec file from the installed <code>device-specs</code>
+ folder, follow the comments in that file and then save it as
+ <code>/<i>someplace</i>/device-specs/specs-<i>mydevice</i></code>.</li>
+ <li>Add <code>-B /<i>someplace</i> -mmcu=<i>mydevice</i></code> to the
+ compiler's command-line options. Notice that
<code>/<i>someplace</i></code>
+ must specify an absolute path and that <code><i>mydevice</i></code>
must
+ not start with "<code>avr</code>".</li>
+ <li>Provided you have a device-specific library
+ <code>lib<i>mydevice</i>.a</code> available, you can put it at
+ <code>/<i>someplace</i></code>, dito for a device-specific startup
+ file <code>crt<i>mydevice</i>.o</code>.</li>
+ </ol>
+ The contents of the device spec files depend on the compiler's
+ configuration, in particular on <code>--with-avrlibc=no</code> and
+ whether or not it is configured for RTEMS.
</li>
<li>A new command-line option <code>-nodevicelib</code> has been added.
It prevents the compiler from linking against AVR-LibC's
@@ -767,13 +769,14 @@ here</a>.</p>
<dd>Specify the flash size of the device in units of 64 KiB,
rounded up to the next integer as needed. This option affects the
availability of the
- <a
href="https://gcc.gnu.org/onlinedocs/gcc/Named-Address-Spaces.html";>AVR
- address-spaces</a>.</dd>
+ <a href="https://gcc.gnu.org/onlinedocs/gcc/Named-Address-Spaces.html";
+ >AVR address-spaces</a>.</dd>
<dt><code>-mskip-bug</code></dt>
<dd>Set if the device is affected by the respective silicon bug.</dd>
</dl>
- In general, you don't need to set these options by hand. The new
- device-specific spec file will set them as needed.
+ These options are used internally in order to communicate between
+ the compiler and the device-spces file.
+ They are set in the device-specs file as needed. Don't set them by hand.
</li>
</ul>
-----------------------------------------------------------------------
Summary of changes:
htdocs/gcc-5/changes.html | 65 +++++++++++++++++++++++++----------------------
1 file changed, 34 insertions(+), 31 deletions(-)
hooks/post-receive
--
gcc-wwwdocs
