public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "nils.smeds at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/103438] Updated documentation for gcc Optimization command line options (sec 3.11)
Date: Thu, 02 Dec 2021 12:56:10 +0000 [thread overview]
Message-ID: <bug-103438-4-Mw4vbfMzDQ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-103438-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103438
--- Comment #10 from Nils Smeds <nils.smeds at gmail dot com> ---
Is there a benefit to augment the -Q output as follows?
[tooladmin@login2302 build]$ diff -r -p a b
diff -r -p a/gcc/opts.c b/gcc/opts.c
*** a/gcc/opts.c Wed Jul 28 08:55:07 2021
--- b/gcc/opts.c Thu Dec 2 13:50:34 2021
*************** print_filtered_help (unsigned int includ
*** 1531,1536 ****
--- 1531,1538 ----
strcat (new_help, _("[enabled]"));
else if (ena == 0)
strcat (new_help, _("[disabled]"));
+ else
+ strcat (new_help, _("[deferred]"))
}
}
------
This should lead to the following diff:
- -fdelete-null-pointer-checks [enabled]
+ -fdelete-null-pointer-checks [deferred]
@@ -332 +332 @@
- -fleading-underscore [enabled]
+ -fleading-underscore [deferred]
@@ -393 +393 @@
- -fprefetch-loop-arrays [enabled]
+ -fprefetch-loop-arrays [deferred]
@@ -502 +502 @@
- -fstrict-volatile-bitfields [enabled]
+ -fstrict-volatile-bitfields [deferred]
@@ -533 +533 @@
- -ftree-loop-if-convert [enabled]
+ -ftree-loop-if-convert [deferred]
Indicating to the user that he/she should dig further if they are interested to
find out how/if the option is in effect.
next prev parent reply other threads:[~2021-12-02 12:56 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-26 11:27 [Bug c/103438] New: " nils.smeds at gmail dot com
2021-11-26 11:35 ` [Bug middle-end/103438] " pinskia at gcc dot gnu.org
2021-11-26 11:36 ` redi at gcc dot gnu.org
2021-11-26 11:37 ` pinskia at gcc dot gnu.org
2021-11-26 11:48 ` nils.smeds at gmail dot com
2021-11-26 12:35 ` rguenth at gcc dot gnu.org
2021-11-26 12:46 ` marxin at gcc dot gnu.org
2021-11-26 13:20 ` nils.smeds at gmail dot com
2021-11-26 21:42 ` nils.smeds at gmail dot com
2021-11-29 15:17 ` marxin at gcc dot gnu.org
2021-12-02 12:56 ` nils.smeds at gmail dot com [this message]
2021-12-02 13:32 ` nils.smeds at gmail dot com
2021-12-02 14:02 ` marxin at gcc dot gnu.org
2021-12-02 14:03 ` nils.smeds at gmail dot com
2021-12-02 14:06 ` nils.smeds at gmail dot com
2021-12-07 13:38 ` cvs-commit at gcc dot gnu.org
2021-12-07 13:39 ` marxin at gcc dot gnu.org
2022-07-08 12:51 ` marxin at gcc dot gnu.org
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=bug-103438-4-Mw4vbfMzDQ@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).