[gcc r14-6480] multiflags: fix doc warning properly
Alexandre Oliva
aoliva@gcc.gnu.org
Wed Dec 13 04:38:56 GMT 2023
https://gcc.gnu.org/g:8e0568d8ac9dbfc8199f970c5c7f26b9735e0e7b
commit r14-6480-g8e0568d8ac9dbfc8199f970c5c7f26b9735e0e7b
Author: Alexandre Oliva <oliva@adacore.com>
Date: Wed Dec 13 01:31:41 2023 -0300
multiflags: fix doc warning properly
Rather than a dubious fix for a dubious warning, namely adding a
period after a parenthesized @xref because the warning demands it, use
@pxref that is meant for exactly this case. Thanks to Joseph Myers
for introducing me to it.
for gcc/ChangeLog
* doc/invoke.texi (multiflags): Drop extraneous period, use
@pxref instead.
Diff:
---
gcc/doc/invoke.texi | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/gcc/doc/invoke.texi b/gcc/doc/invoke.texi
index 1f26f80d26c..19feba467a4 100644
--- a/gcc/doc/invoke.texi
+++ b/gcc/doc/invoke.texi
@@ -20588,8 +20588,8 @@ allocation before or after interprocedural optimization.
@item -fmultiflags
This option enables multilib-aware @code{TFLAGS} to be used to build
target libraries with options different from those the compiler is
-configured to use by default, through the use of specs (@xref{Spec
-Files}.) set up by compiler internals, by the target, or by builders at
+configured to use by default, through the use of specs (@pxref{Spec
+Files}) set up by compiler internals, by the target, or by builders at
configure time.
Like @code{TFLAGS}, this allows the target libraries to be built for
More information about the Gcc-cvs
mailing list