public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bernardo Innocenti <bernie@develer.com>
To: Aaron Lehmann <aaronl@vitelus.com>
Cc: gcc@gcc.gnu.org, linux-kernel@vger.kernel.org
Subject: Re: Big kernel size increase with gcc 3.4
Date: Fri, 08 Aug 2003 16:00:43 +0200	[thread overview]
Message-ID: <3F33AD0B.8020501@develer.com> (raw)
In-Reply-To: <20030808024909.GT2712@vitelus.com>

Aaron Lehmann wrote:
> On Fri, Aug 08, 2003 at 04:39:02AM +0200, Bernardo Innocenti wrote:
> 
>>- same optimization flags: -m5307 -O2 -fno-strict-aliasing
>>     -fno-common -fno-builtin -fomit-frame-pointer
> 
> You should try -Os if you want to optimize for size.

I did some time ago, and it seems to reduce the code size greatly,
but then I noticed some problems with the memory allocator and
switched back to -O2 for fear that changing the inlining policy
could lead to instability.

I still see those memory allocator problems, so I think I could
safely switch back to -Os now... actually I would recommend it
for all embedded targets.

-- 
  // 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




  reply	other threads:[~2003-08-08 14:00 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 [this message]
     [not found]   ` <20030808053327.GZ150921@niksula.cs.hut.fi>
2003-08-08 15:10     ` Bernardo Innocenti
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=3F33AD0B.8020501@develer.com \
    --to=bernie@develer.com \
    --cc=aaronl@vitelus.com \
    --cc=gcc@gcc.gnu.org \
    --cc=linux-kernel@vger.kernel.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