public inbox for gcc-cvs-wwwdocs@sourceware.org help / color / mirror / Atom feed
From: Jonathan Wakely <redi@sourceware.org> To: gcc-cvs-wwwdocs@gcc.gnu.org Subject: gcc-wwwdocs branch master updated. 9f1723bc1d6b52fcfcfc4a8aee93eada98412e78 Date: Mon, 7 Jun 2021 14:46:59 +0000 (GMT) [thread overview] Message-ID: <20210607144659.62B553835414@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 9f1723bc1d6b52fcfcfc4a8aee93eada98412e78 (commit) from bbbf05e7f3d3e7a74d23e8cc252ebae895158abe (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 9f1723bc1d6b52fcfcfc4a8aee93eada98412e78 Author: Jonathan Wakely <jwakely@redhat.com> Date: Mon Jun 7 11:00:22 2021 +0100 Add HTML anchors to GCC 5 "porting to" notes diff --git a/htdocs/gcc-5/porting_to.html b/htdocs/gcc-5/porting_to.html index 7d629e78..c359dfb2 100644 --- a/htdocs/gcc-5/porting_to.html +++ b/htdocs/gcc-5/porting_to.html @@ -28,7 +28,7 @@ manner. Additions and suggestions for improvement are welcome. </p> -<h2>Preprocessor issues</h2> +<h2 id="cpp">Preprocessor issues</h2> <p>The preprocessor started to emit line markers to properly distinguish whether a macro token comes from a system header, or from a normal header @@ -65,9 +65,9 @@ Observe how the <code>exitfailure</code> and <code>1</code> tokens are not on the same line anymore. -<h2>C language issues</h2> +<h2 id="c">C language issues</h2> -<h3>Default standard is now GNU11</h3> +<h3 id="gnu11">Default standard is now GNU11</h3> <p>GCC defaults to <code>-std=gnu11</code> instead of <code>-std=gnu89</code>. This brings several changes that users should be aware of. The following @@ -84,7 +84,7 @@ former warns about features not present in ISO C90, but present in ISO C99. The latter warns about features not present in ISO C99, but present in ISO C11. See the GCC manual for more info.</p> -<h4>Different semantics for inline functions</h4> +<h4 id="inline">Different semantics for inline functions</h4> <p>While <code>-std=gnu89</code> employs the GNU89 inline semantics, <code>-std=gnu11</code> uses the C99 inline semantics. The C99 inline semantics @@ -184,7 +184,7 @@ standard due to multiple definition errors:</p> } </code></pre> -<h4>Some warnings are enabled by default</h4> +<h4 id="default-warnings">Some warnings are enabled by default</h4> <p>The C99 mode enables some warnings by default. For instance, GCC warns about missing declarations of functions:</p> @@ -267,7 +267,7 @@ returning no value in a function returning non-void:</p> <p>The fix is either to specify a proper return value, or to declare the return type of <code>foo</code> as <code>void</code>.</p> -<h4>Initializing statics with compound literals</h4> +<h4 id="complit">Initializing statics with compound literals</h4> <p>Previously, initializing objects with static storage duration with compound literals was only allowed in the GNU89 mode. This restriction has been lifted @@ -296,7 +296,7 @@ snippet is an example of such initialization:</p> <span class="boldlime">^</span> </pre> -<h4><code>__STDC_VERSION__</code> macro</h4> +<h4 id="version-macro"><code>__STDC_VERSION__</code> macro</h4> <p>As the default mode changed to C11, the <code>__STDC_VERSION__</code> standard macro, introduced in C95, is now defined by default, and has @@ -314,7 +314,7 @@ the value <code>201112L</code>.</p> <p>You can check the macro using <code>gcc -dM -E -std=gnu11 - < /dev/null | grep STDC_VER</code>.</p> -<h4>Different meaning of the <code>%a *scanf</code> conversion specification</h4> +<h4 id="scanf">Different meaning of the <code>%a *scanf</code> conversion specification</h4> <p>In C89, the GNU C library supports dynamic allocation via the <code>%as</code>, <code>%aS</code>, and <code>%a[...]</code> conversion specifications; see @@ -346,7 +346,7 @@ This is a change in semantics, and in combination with the <code>m</code> as a length modifier as per POSIX.1-2008. That is, use <code>%ms</code> or <code>%m[...]</code>.</p> -<h3>New warnings</h3> +<h3 id="new-warnings">New warnings</h3> <p>Several new warnings have been added to the C front end. Among others <code>-Wpedantic</code> now warns about non-standard predefined identifiers. @@ -374,9 +374,9 @@ For instance:</p> </code></pre> -<h2>C++ language issues</h2> +<h2 id="cxx">C++ language issues</h2> -<h3>Converting <code>std::nullptr_t</code> to <code>bool</code></h3> +<h3 id="nullptr">Converting <code>std::nullptr_t</code> to <code>bool</code></h3> <p>Converting <code>std::nullptr_t</code> to <code>bool</code> in C++11 mode now requires direct-initialization. This has been changed in @@ -397,7 +397,7 @@ mode now requires direct-initialization. This has been changed in It is recommended to use the <code>false</code> keyword instead of converting <code>nullptr</code> to <code>bool</code>. -<h3>Return by converting move constructor</h3> +<h3 id="dr1579">Return by converting move constructor</h3> <p>GCC 5 implements <a href="http://www.open-std.org/jtc1/sc22/wg21/docs/cwg_defects.html#1579">DR 1579</a> @@ -430,7 +430,7 @@ using <code>return X(y);</code> or </p> -<h2>Links</h2> +<h2 id="links">Links</h2> <p> Marek Polacek and Jakub Jelinek, ----------------------------------------------------------------------- Summary of changes: htdocs/gcc-5/porting_to.html | 26 +++++++++++++------------- 1 file changed, 13 insertions(+), 13 deletions(-) hooks/post-receive -- gcc-wwwdocs
reply other threads:[~2021-06-07 14:46 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=20210607144659.62B553835414@sourceware.org \ --to=redi@sourceware.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: linkBe 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).