public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Dave Korn" <dk@artimi.com>
To: "'gcc_mailing_list'" <gcc@gcc.gnu.org>
Subject: RE: optimization issue about -O2 and -Os
Date: Fri, 30 Apr 2004 19:45:00 -0000	[thread overview]
Message-ID: <NUTMEGNN79xavjrRZ1U00000115@NUTMEG.CAM.ARTIMI.COM> (raw)
In-Reply-To: <87y8odiepk.fsf@egil.codesourcery.com>

> -----Original Message-----
> From: Zack Weinberg 
> Sent: 30 April 2004 18:00

> "Dave Korn" <> writes:
> 
> >
> >   Ah, I stand corrected.  Would it be accurate to say that 
> they are _both_
> > shorthand for a set of -f options _and_ _also_ control a 
> set of other
> > behaviours, which entail enabling, disabling, or 
> fine-tuning the parameters
> > of other optimisations that do not correspond directly to 
> -f options ?
> 
> Yeah, that's pretty accurate.  You can look through the source code
> for instances of the global flags "optimize" and "optimize_size".
> Anything you can do to improve the documentation in this regard would
> be much appreciated.  It would probably be a good move to deemphasize
> all those -f switches; they tend not to be all that useful; I consider
> their primary purpose to be working around bugs in specific
> optimizations, using -On -fno-<buggy-pass>.
> 
> zw


  Hmm, maybe it would be worthwhile to invent -f options for all these
ad-hoc tests on the optimize variables, so that the -O options then *did*
become shorthand for flag sets, and the suggestion I already made for
localising the failure with a given -O setting would actually work?


    cheers, 
      DaveK
-- 
Can't think of a witty .sigline today....

  reply	other threads:[~2004-04-30 17:23 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-29 10:33 Ebony Zhu
2004-04-30  0:37 ` Jim Wilson
2004-04-30  6:39   ` Ebony Zhu
2004-04-30  9:20     ` Jim Wilson
2004-04-30 13:23       ` Ebony Zhu
2004-04-30 16:06       ` Dave Korn
2004-04-30 16:42         ` Zack Weinberg
2004-04-30 18:09           ` Dave Korn
2004-04-30 19:12             ` Zack Weinberg
2004-04-30 19:45               ` Dave Korn [this message]
2004-04-30 20:05                 ` Phil Edwards
2004-04-30 20:09                   ` David Edelsohn
2004-04-30 21:02                   ` llewelly
2004-04-30 18:29       ` Dale Johannesen

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=NUTMEGNN79xavjrRZ1U00000115@NUTMEG.CAM.ARTIMI.COM \
    --to=dk@artimi.com \
    --cc=gcc@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).