linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Robert Love <rml@tech9.net>
To: Christoph Hellwig <hch@infradead.org>
Cc: Marcus Meissner <mm@ns.caldera.de>, linux-kernel@vger.kernel.org
Subject: Re: Compiling 2.2.19 with -O3 flag
Date: 24 May 2002 10:55:20 -0700	[thread overview]
Message-ID: <1022262920.956.258.camel@sinai> (raw)
In-Reply-To: <20020524184402.A24780@infradead.org>

On Fri, 2002-05-24 at 10:44, Christoph Hellwig wrote:

> -Os implies -O2 + additional size-reducing features:
> 
> [hch@sb hch]$ grep -r optimize_size /work/people/hch/gcc/gcc | wc -l
>     250
> [hch@sb hch]$
> 
> A bunch of matches are in ChangeLog and most are target-specific,
> but I guess you got the point..

I know this...maybe I am not being clear.  I realize -Os is a derivate
of -O2, but is it not an interesting note if -Os can be as fast (or
faster) than -O2 and still generate smaller binaries?  That is my point.

If -Os is equivalent in speed to -O2 but also generates smaller objects,
then why have -O2?  If it does not generate smaller objects (which is
what my testing has shown) then it is worthless.  Unless it is faster
than -O2, like Alan said, in which case then the two options need to
rethink themselves ;-)

	Robert Love


  reply	other threads:[~2002-05-24 17:55 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-24  6:51 Compiling 2.2.19 with -O3 flag samson swanson
2002-05-24 14:42 ` Alan Cox
2002-05-24 15:19   ` Robert Love
2002-05-24 15:44     ` Alan Cox
2002-05-24 16:45     ` Marcus Meissner
2002-05-24 16:54       ` Robert Love
2002-05-24 17:44         ` Christoph Hellwig
2002-05-24 17:55           ` Robert Love [this message]
2002-05-24 18:00             ` Christoph Hellwig

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=1022262920.956.258.camel@sinai \
    --to=rml@tech9.net \
    --cc=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mm@ns.caldera.de \
    /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 NNTP newsgroup(s).