public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: llewelly@xmission.com
To: gcc@gcc.gnu.org
Cc: Dave Korn <dk@artimi.com>
Subject: Re: optimization issue about -O2 and -Os
Date: Fri, 30 Apr 2004 21:02:00 -0000	[thread overview]
Message-ID: <s3rhdv1uwxp.fsf@xmission.xmission.com> (raw)
In-Reply-To: <20040430181516.GB10422@disaster.jaj.com>

Phil Edwards <phil@codesourcery.com> writes:

> On Fri, Apr 30, 2004 at 06:21:26PM +0100, Dave Korn wrote:
> > 
> >   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?
> 
> We need fewer -f options, really, not more of them.
> 
> Or to put it another way:  if an optimization pass is buggy, it doesn't
> deserve to have an -f option yet.
[snip]

From the standpoint of a user, if an optimization pass is buggy, it
    needs an -fno option.

  parent reply	other threads:[~2004-04-30 18:45 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
2004-04-30 20:05                 ` Phil Edwards
2004-04-30 20:09                   ` David Edelsohn
2004-04-30 21:02                   ` llewelly [this message]
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=s3rhdv1uwxp.fsf@xmission.xmission.com \
    --to=llewelly@xmission.com \
    --cc=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).