From: <tm_gccmail@mail.kloo.net>
To: Bernardo Innocenti <bernie@develer.com>
Cc: gcc@gcc.gnu.org, linux-kernel@vger.kernel.org
Subject: Re: Big kernel size increase with gcc 3.4
Date: Fri, 8 Aug 2003 12:24:09 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.21.0308081223260.29338-100000@mail.kloo.net> (raw)
In-Reply-To: <3F330D46.8020508@develer.com>
On Fri, 8 Aug 2003, Bernardo Innocenti wrote:
> Hello,
>
> these figures speak for themselves:
>
> text data bss dec hex filename
> 833352 47200 78884 959436 ea3cc linux-2.6.x/vmlinux_gcc331
> 877420 53212 78884 1009516 f676c linux-2.6.x/vmlinux_gcc34
>
>
> - target is linux-2.6.0-test2-uc0 for m68knommu (full config
> available on request);
>
> - same optimization flags: -m5307 -O2 -fno-strict-aliasing
> -fno-common -fno-builtin -fomit-frame-pointer
Could you add -fno-reorder-blocks and report the result?
Toshi
prev parent reply other threads:[~2003-08-08 19:37 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
2003-08-08 19:24 ` tm_gccmail [this message]
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=Pine.LNX.4.21.0308081223260.29338-100000@mail.kloo.net \
--to=tm_gccmail@mail.kloo.net \
--cc=bernie@develer.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;
as well as URLs for NNTP newsgroup(s).