diff mbox

[wwwdocs] Add gcc-5 caveats for avr.

Message ID 5534D76F.2060503@gjlay.de
State New
Headers show

Commit Message

Georg-Johann Lay April 20, 2015, 10:39 a.m. UTC
Hi Gerald, this is the patch against GCC-5's release notes.

Okay to install?

Johann

Comments

Andi Kleen April 20, 2015, 1:40 p.m. UTC | #1
Georg-Johann Lay <avr@gjlay.de> writes:
> +        <a href="http://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&nbsp;5.2 and a version of AVR-LibC which implements

Really 5.2?

-Andi
Georg-Johann Lay April 20, 2015, 4:21 p.m. UTC | #2
Am 04/20/2015 um 03:40 PM schrieb Andi Kleen:
> Georg-Johann Lay <avr@gjlay.de> writes:
>> +        <a href="http://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&nbsp;5.2 and a version of AVR-LibC which implements
>
> Really 5.2?
>
> -Andi


It is still unclear to me whether changes to 3ary platforms may go into 5.1.  See

https://gcc.gnu.org/ml/gcc-patches/2015-04/msg00908.html

Johann
Jakub Jelinek April 20, 2015, 4:30 p.m. UTC | #3
On Mon, Apr 20, 2015 at 06:21:30PM +0200, Georg-Johann Lay wrote:
> Am 04/20/2015 um 03:40 PM schrieb Andi Kleen:
> >Georg-Johann Lay <avr@gjlay.de> writes:
> >>+        <a href="http://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&nbsp;5.2 and a version of AVR-LibC which implements
> >
> >Really 5.2?
> >
> >-Andi
> 
> 
> It is still unclear to me whether changes to 3ary platforms may go into 5.1.  See
> 
> https://gcc.gnu.org/ml/gcc-patches/2015-04/msg00908.html

At this point no.

	Jakub
Gerald Pfeifer April 20, 2015, 7:02 p.m. UTC | #4
Hi Johann,

On Mon, 20 Apr 2015, Georg-Johann Lay wrote:
> Okay to install?

+    <li>The AVR port uses a new scheme to describe supported devices:
+        For each supported device the compiler provides a device-specific
+        <a href="http://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&nbsp;5.2 and a version of AVR-LibC which implements
+        <a href="http://savannah.nongnu.org/bugs/?44574"</a>#44574</a>.</li>

Can you please make the two links https-links?  (Especially the
one to gcc.gnu.org actually redirects.)

Just using "#44574" for a reference, may that be a little confusing,
or is it sufficiently clear to AVR users?

+  <li>A new command option <code>-nodevicelib</code> has been added.

"command-line option"

+    If this option is turned on the compiler won't link against AVR-LibC's
+    device-specific library <code>lib<i>device</i>.a</code> by omitting
+    <code>-l<i>device</i></code> from the linker's command line.

How about making this "...-nodevicelib</code> prevents the compiler
from linking against...."?

+    If the compiler had not been
+    <a href="http://gcc.gnu.org/install/configure.html">configured</a>
+    to be used with AVR-LibC, the compiler will not link against that
+    library and the option has no effect.</li>

"was not" (or "is") instead of "had not", and can you please use
https here as well?

Though, really, could this be just simplified to "If the compiler is
not configured for use with AVR-LibC to begin with, this option has 
no effect"?


Your patch is fine with the above changes or considering them and
deciding not go for one or the other.

Gerald
diff mbox

Patch

Index: gcc-5/changes.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-5/changes.html,v
retrieving revision 1.109
diff -u -p -r1.109 changes.html
--- gcc-5/changes.html	20 Apr 2015 08:22:35 -0000	1.109
+++ gcc-5/changes.html	20 Apr 2015 10:34:45 -0000
@@ -28,6 +28,14 @@ 
         <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&nbsp;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="http://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&nbsp;5.2 and a version of AVR-LibC which implements
+        <a href="http://savannah.nongnu.org/bugs/?44574"</a>#44574</a>.</li>
   </ul>
 
 <h2 id="general">General Optimizer Improvements</h2>
@@ -690,6 +698,18 @@  here</a>.</p>
      </li>
      </ul>
 
+<h3 id="avr">AVR</h3>
+<ul>
+  <li>A new command option <code>-nodevicelib</code> has been added.
+    If this option is turned on the compiler won't link against AVR-LibC's
+    device-specific library <code>lib<i>device</i>.a</code> by omitting
+    <code>-l<i>device</i></code> from the linker's command line.
+    If the compiler had not been
+    <a href="http://gcc.gnu.org/install/configure.html">configured</a>
+    to be used with AVR-LibC, the compiler will not link against that
+    library and the option has no effect.</li>
+</ul>
+
 <h3 id="x86">IA-32/x86-64</h3>
   <ul>
     <li>New ISA extensions support