From: Joseph Myers <joseph@codesourcery.com>
To: Martin Sebor <msebor@gmail.com>
Cc: Alexander Monakov <amonakov@ispras.ru>,
Gcc Patch List <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] clarify documentation of -Q --help=optimizers
Date: Thu, 05 Nov 2015 00:54:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.10.1511050053500.18787@digraph.polyomino.org.uk> (raw)
In-Reply-To: <563A9A31.5060306@gmail.com>
On Wed, 4 Nov 2015, Martin Sebor wrote:
> Improving the compiler output is a good idea. The attached patch
> prints "[disabled by -O0]" instead of "[enabled]" when an optimization
> option is enabled by default but when optimization (i.e., -O1 or
> greater) is not enabled.
I don't think it's entirely accurate that all options marked as
Optimization in *.opt are actually disabled by -O0. Many are, but it
depends on the actual logic controlling each optimization.
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2015-11-05 0:54 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <56299713.6040204@gmail.com>
2015-10-23 3:56 ` Martin Sebor
2015-11-02 21:48 ` [PING] " Martin Sebor
2015-11-03 10:19 ` Alexander Monakov
2015-11-04 23:52 ` Martin Sebor
2015-11-05 0:54 ` Joseph Myers [this message]
2015-11-05 10:48 ` Alexander Monakov
2015-11-05 15:58 ` Martin Sebor
2015-11-05 17:09 ` Segher Boessenkool
2015-11-05 21:04 ` Martin Sebor
2015-11-05 23:30 ` Segher Boessenkool
2015-11-06 1:25 ` Martin Sebor
2015-11-05 17:11 ` Joseph Myers
2015-11-05 17:47 ` Martin Sebor
2015-11-05 18:07 ` Joseph Myers
2015-11-05 18:45 ` Martin Sebor
2015-11-05 18:47 ` Joseph Myers
2015-11-05 1:09 ` Sandra Loosemore
2015-11-05 2:40 ` Martin Sebor
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=alpine.DEB.2.10.1511050053500.18787@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=amonakov@ispras.ru \
--cc=gcc-patches@gcc.gnu.org \
--cc=msebor@gmail.com \
/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).