From: Bernardo Innocenti <bernie@develer.com>
To: gcc@gcc.gnu.org
Cc: linux-kernel@vger.kernel.org
Subject: Big kernel size increase with gcc 3.4
Date: Fri, 08 Aug 2003 04:39:02 +0200 [thread overview]
Message-ID: <3F330D46.8020508@develer.com> (raw)
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
- same ColdFire GCC patches were used (I strongly doubt it
could be a back-end issue);
- gcc-3.3.1-20030720 VS gcc-3.4-20030806.
I can provide more datails if needed. Could be an inlining issue
of course.
Out of curiosity, it seems that the old 2.95.3 could finally be
sent to rest now:
text data bss dec hex filename
833352 47200 78884 959436 ea3cc linux-2.6.x/vmlinux_gcc331
857208 72800 60836 990844 f1e7c linux-2.6.x/vmlinux_gcc295
--
// 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
next reply other threads:[~2003-08-08 2:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-08 2:39 Bernardo Innocenti [this message]
2003-08-08 2:49 ` Big kernel size increase with gcc 3.4 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
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=3F330D46.8020508@develer.com \
--to=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).