public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Alexandre Oliva <aoliva@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc(refs/users/aoliva/heads/testme)] multiflags: fix doc warning
Date: Sat,  9 Dec 2023 05:22:17 +0000 (GMT)	[thread overview]
Message-ID: <20231209052217.790903858413@sourceware.org> (raw)

https://gcc.gnu.org/g:268954546c6debfe20a118dc1268ae58c86a3506

commit 268954546c6debfe20a118dc1268ae58c86a3506
Author: Alexandre Oliva <oliva@adacore.com>
Date:   Fri Dec 8 23:37:35 2023 -0300

    multiflags: fix doc warning
    
    Comply with dubious doc warning that after an @xref there must be a
    comma or a period, not a close parentheses.
    
    
    for  gcc/ChangeLog
    
            * doc/invoke.texi (multiflags): Add period after @xref to
            silence warning.

Diff:
---
 gcc/doc/invoke.texi | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/gcc/doc/invoke.texi b/gcc/doc/invoke.texi
index d4e689b64c0..4e67c95dbf8 100644
--- a/gcc/doc/invoke.texi
+++ b/gcc/doc/invoke.texi
@@ -20589,7 +20589,7 @@ allocation before or after interprocedural optimization.
 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
+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

             reply	other threads:[~2023-12-09  5:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-09  5:22 Alexandre Oliva [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-12-11 16:09 Alexandre Oliva
2023-12-09  5:03 Alexandre Oliva

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=20231209052217.790903858413@sourceware.org \
    --to=aoliva@gcc.gnu.org \
    --cc=gcc-cvs@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: link
Be 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).