diff mbox series

[pushed] wwwdocs: gcc-14/porting_to: Improve markup.

Message ID 20240505214133.CDF4133E8D@hamza.pair.com
State New
Headers show
Series [pushed] wwwdocs: gcc-14/porting_to: Improve markup. | expand

Commit Message

Gerald Pfeifer May 5, 2024, 9:41 p.m. UTC 
The key change is putting "GCC target" in <code> ... </code>.

Pushed.

Gerald

---
 htdocs/gcc-14/porting_to.html | 16 +++++++---------
 1 file changed, 7 insertions(+), 9 deletions(-)
diff mbox series

Patch

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> -->