public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "Thomas dot Koenig at online dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug driver/19848] "options passed" from -verbose-asm do not adequately reflect optimization
Date: Thu, 10 Feb 2005 14:15:00 -0000 [thread overview]
Message-ID: <20050210085236.16853.qmail@sourceware.org> (raw)
In-Reply-To: <20050209124042.19848.Thomas.Koenig@online.de>
------- Additional Comments From Thomas dot Koenig at online dot de 2005-02-10 08:52 -------
(In reply to comment #2)
> There are a gazillion places where we just check "if (optimize)" without
> any specific flag. It would be quite a lot of work to introduce flags for all
> of them, and I'm not sure it's worth it...
$ find . -name '*.c' | xargs grep '( *optimize[) =!><|&]' | wc -l
151
Hmm...
It would still be better if this could be at least lumped into an
option (maybe -foptimize-misc or whatever) which would still be
visible in -fverbose-asm.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19848
next prev parent reply other threads:[~2005-02-10 8:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-09 17:48 [Bug driver/19848] New: " Thomas dot Koenig at online dot de
2005-02-09 17:50 ` [Bug driver/19848] " Thomas dot Koenig at online dot de
2005-02-10 0:44 ` Thomas dot Koenig at online dot de
2005-02-10 1:13 ` falk at debian dot org
2005-02-10 14:15 ` Thomas dot Koenig at online dot de [this message]
2005-02-10 17:21 ` schwab at suse dot de
2005-02-10 23:13 ` Thomas dot Koenig at online dot de
2005-02-10 23:14 ` Thomas dot Koenig at online dot de
[not found] <bug-19848-9515@http.gcc.gnu.org/bugzilla/>
2005-10-07 7:30 ` jvdelisle at gcc dot gnu dot org
2007-11-14 2:39 ` manu at gcc dot gnu dot 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=20050210085236.16853.qmail@sourceware.org \
--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).