This is a little follow up to Alexandre's note for the GCC 11 release
notes - we usually mark command-line options as <code>.
Pushed.
Gerald
---
htdocs/gcc-11/changes.html | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/htdocs/gcc-11/changes.html b/htdocs/gcc-11/changes.html
index 2f00d1f1..9dba1e14 100644
--- a/htdocs/gcc-11/changes.html
+++ b/htdocs/gcc-11/changes.html
@@ -32,8 +32,9 @@ a work-in-progress.</p>
<ul>
<li>Naming and location of auxiliary and dump output files changed.
If you compile multiple input files in a single command, if you
- enable Link Time Optimization, or if you use -dumpbase,
- -dumpdir, -save-temps=*, and you expect any file other than the
+ enable Link Time Optimization, or if you use <code>-dumpbase</code>,
+ <code>-dumpdir</code>, <code>-save-temps=*</code>, and you expect
+ any file other than the
primary output file(s) to be created as a side effect, watch out
for improvements and a few surprises.
See <a
href="https://gcc.gnu.org/pipermail/gcc-patches/2020-May/546494.html";>the
--
2.26.2
