Re: [PATCH] multiflags: fix doc warning properly

2023-12-12 Thread Joseph Myers
On Mon, 11 Dec 2023, Alexandre Oliva wrote: > On Dec 11, 2023, Joseph Myers wrote: > > > On Fri, 8 Dec 2023, Alexandre Oliva wrote: > >> @@ -20589,7 +20589,7 @@ allocation before or after interprocedural > >> optimization. > >> This option enables multilib-aware @code{TFLAGS} to be used to

[PATCH] multiflags: fix doc warning properly

2023-12-11 Thread Alexandre Oliva
On Dec 11, 2023, Joseph Myers wrote: > On Fri, 8 Dec 2023, Alexandre Oliva wrote: >> @@ -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

Re: [PATCH] multiflags: fix doc warning

2023-12-11 Thread Joseph Myers
On Fri, 8 Dec 2023, Alexandre Oliva wrote: > @@ -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

Re: [PATCH] multiflags: fix doc warning

2023-12-10 Thread Jeff Law
On 12/8/23 19:48, Alexandre Oliva wrote: Comply with dubious doc warning that after an @xref there must be a comma or a period, not a close parentheses. Build-testing on x86_64-linux-gnu now. Ok to install? for gcc/ChangeLog * doc/invoke.texi (multiflags): Add period after

[PATCH] multiflags: fix doc warning

2023-12-08 Thread Alexandre Oliva
Comply with dubious doc warning that after an @xref there must be a comma or a period, not a close parentheses. Build-testing on x86_64-linux-gnu now. Ok to install? for gcc/ChangeLog * doc/invoke.texi (multiflags): Add period after @xref to silence warning. ---