On 05/12/19 13:14 +0000, Wilco Dijkstra wrote:
Hi,Add entries for the default change in changes.html and porting_to.html. Passes the W3 validator. Cheers, Wilco --- diff --git a/htdocs/gcc-10/changes.html b/htdocs/gcc-10/changes.html index e02966460450b7aad884b2d45190b9ecd8c7a5d8..304e1e8ccd38795104156e86b92062696fa5aa8b 100644 --- a/htdocs/gcc-10/changes.html +++ b/htdocs/gcc-10/changes.html @@ -102,6 +102,11 @@ a work-in-progress.</p> <li>In C2X mode, <code>-fno-fp-int-builtin-inexact</code> is enabled by default.</li> </ul></li> + + <li>GCC now defaults to <code>-fno-common</code>. In C, global variables with + multiple tentative definitions will result in linker errors. + Global variable accesses are also more efficient on various targets.
The "also" here is a bit unclear what it refers to. It seems to follow on from the previous sentence, which suggests that the efficiencies are somehow related to the cases that get linker errors. How about: GCC now defaults to <code>-fno-common</code>. As a result, global variable accesses are more efficient on various targets. In C, global variables with multiple tentative definitions will result in linker errors.
+ </li> </ul> <h3 id="cxx">C++</h3> diff --git a/htdocs/gcc-10/porting_to.html b/htdocs/gcc-10/porting_to.html index 3256e8a35d00ce1352c169a1c6df6d8f120889ee..e2c7e226a83b7720fe6ed40061cdddbc27659664 100644 --- a/htdocs/gcc-10/porting_to.html +++ b/htdocs/gcc-10/porting_to.html @@ -29,9 +29,25 @@ and provide solutions. Let us know if you have suggestions for improvements! <h2 id="cpp">Preprocessor issues</h2> --> -<!-- <h2 id="c">C language issues</h2> ---> + +<h3 id="complit">Default to <code>-fno-common</code></h3>
What does "complit" mean? Would a more memorable anchor such as "common" or "no-common" be better?
