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)] [docs] note that -g opts are implicitly negatable too
Date: Fri, 20 Jan 2023 18:50:12 +0000 (GMT)	[thread overview]
Message-ID: <20230120185012.31DED3858416@sourceware.org> (raw)

https://gcc.gnu.org/g:43ad467068ca53d8c87680797dbd8283dd271d82

commit 43ad467068ca53d8c87680797dbd8283dd271d82
Author: Alexandre Oliva <oliva@gnu.org>
Date:   Fri Jan 20 15:41:37 2023 -0300

    [docs] note that -g opts are implicitly negatable too
    
    Back in 2017, I made -g* options implicitly negatable, without
    realizing there was documentation that required updating.  Oops.
    Fixed, at last!
    
    
    for gcc/ChangeLog
    
            * doc/options.texi (option, RejectNegative): Mention that
            -g-started options are also implicitly negatable.

Diff:
---
 gcc/doc/options.texi | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/gcc/doc/options.texi b/gcc/doc/options.texi
index c6e73fd1818..f50063c9787 100644
--- a/gcc/doc/options.texi
+++ b/gcc/doc/options.texi
@@ -161,7 +161,7 @@ the help text to use for @option{--help} (omitted if the second field
 contains the @code{Undocumented} property).
 @end enumerate
 
-By default, all options beginning with ``f'', ``W'' or ``m'' are
+By default, all options beginning with ``f'', ``g'', ``W'' or ``m'' are
 implicitly assumed to take a ``no-'' form.  This form should not be
 listed separately.  If an option beginning with one of these letters
 does not have a ``no-'' form, you can use the @code{RejectNegative}
@@ -239,8 +239,8 @@ and should not be accepted by the driver.
 
 @item RejectNegative
 The option does not have a ``no-'' form.  All options beginning with
-``f'', ``W'' or ``m'' are assumed to have a ``no-'' form unless this
-property is used.
+``f'', ``g'', ``W'' or ``m'' are assumed to have a ``no-'' form unless
+this property is used.
 
 @item Negative(@var{othername})
 The option will turn off another option @var{othername}, which is

                 reply	other threads:[~2023-01-20 18:50 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20230120185012.31DED3858416@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).