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 b018ddd6e4b85c37ea3129b567c1f67717a40132 (commit)
from 081ae01843bf8ed25ab7135123ab21d817db8fa9 (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 b018ddd6e4b85c37ea3129b567c1f67717a40132
Author: Gerald Pfeifer <ger...@pfeifer.com>
Date: Sun May 5 23:35:48 2024 +0200
gcc-14/porting_to: Improve markup.
diff --git a/htdocs/gcc-14/porting_to.html b/htdocs/gcc-14/porting_to.html
index 13772080..db27f122 100644
--- a/htdocs/gcc-14/porting_to.html
+++ b/htdocs/gcc-14/porting_to.html
@@ -516,18 +516,17 @@ be included explicitly when compiling with GCC 14:
<h3 id="target-pragma">Pragma GCC target now affects preprocessor symbols</h3>
-<p>
-The behavior of pragma GCC target and specifically how it affects ISA
-macros has changed in GCC 14. In GCC 13 and older, the <code>GCC
+<p>The behavior of pragma <code>GCC target</code> and specifically how
+it affects ISA macros has changed in GCC 14. Before the <code>GCC
target</code> pragma defined and undefined corresponding ISA macros in
C when using the integrated preprocessor during compilation but not
when the preprocessor was invoked as a separate step or when using
the <code>-save-temps</code> option. In C++ the ISA macro definitions
-were performed in a way which did not have any actual effect.
+were performed in a way which did not have any actual effect.</p>
-In GCC 14 C++ behaves like C with integrated preprocessing in earlier
+<p>In GCC 14 C++ behaves like C with integrated preprocessing in earlier
versions. Moreover, in both languages ISA macros are defined and
-undefined as expected when preprocessing separately from compilation.
+undefined as expected when preprocessing separately from compilation.</p>
<p>
This can lead to different behavior, especially in C++. For example,
@@ -552,9 +551,8 @@ incorrect instruction set by GCC 14.
which was not intended. */
</pre>
-<p>
-The fix in this case is to remember whether <code>pop_options</code>
-needs to be performed in a new user-defined macro.
+<p>The fix in this case is to remember whether <code>pop_options</code>
+needs to be performed in a new user-defined macro.</p>
<!-- <h2 id="fortran">Fortran language issues</h2> -->
-----------------------------------------------------------------------
Summary of changes:
htdocs/gcc-14/porting_to.html | 16 +++++++---------
1 file changed, 7 insertions(+), 9 deletions(-)
hooks/post-receive
--
gcc-wwwdocs
