All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bernardo Innocenti <bernie@develer.com>
To: Ville Herva <vherva@niksula.hut.fi>
Cc: Aaron Lehmann <aaronl@vitelus.com>,
	gcc@gcc.gnu.org, linux-kernel@vger.kernel.org
Subject: Re: Big kernel size increase with gcc 3.4
Date: Fri, 08 Aug 2003 17:10:15 +0200	[thread overview]
Message-ID: <3F33BD57.8090904@develer.com> (raw)
In-Reply-To: <20030808053327.GZ150921@niksula.cs.hut.fi>

Ville Herva wrote:

>>You should try -Os if you want to optimize for size.
> 
> I was about to suggest that, too.
> 
> It could be that while optimizing for speed, gcc 3.4 simply inlines way more
> by default (whether or not that actually makes the code faster is a
> different question). I think -Os could be a better comparison.

You were both right. With -Os, GCC 3.3.1 and 3.4 perform
similarly, with a slight advantage for 3.4 :-)

   text    data     bss     dec     hex filename
 833352   47200   78884  959436   ea3cc vmlinux_gcc331
 807140   48036   78884  934060   e40ac vmlinux_gcc331_Os
 796264   50560   78884  925708   e200c vmlinux_gcc34_Os

-- 
  // Bernardo Innocenti - Develer S.r.l., R&D dept.
\X/  http://www.develer.com/

Please don't send Word attachments - http://www.gnu.org/philosophy/no-word-attachments.html




  parent reply	other threads:[~2003-08-08 15:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-08  2:39 Big kernel size increase with gcc 3.4 Bernardo Innocenti
2003-08-08  2:49 ` Aaron Lehmann
2003-08-08 14:00   ` Bernardo Innocenti
     [not found]   ` <20030808053327.GZ150921@niksula.cs.hut.fi>
2003-08-08 15:10     ` Bernardo Innocenti [this message]
2003-08-08 19:24 ` tm_gccmail

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=3F33BD57.8090904@develer.com \
    --to=bernie@develer.com \
    --cc=aaronl@vitelus.com \
    --cc=gcc@gcc.gnu.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vherva@niksula.hut.fi \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.