From: josh@joshtriplett.org
To: Joe Perches <joe@perches.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: tinyconfig x86-32 vmlinux sizes by gcc compiler version
Date: Thu, 4 Dec 2014 14:25:21 -0800 [thread overview]
Message-ID: <20141204222521.GA20091@cloud> (raw)
In-Reply-To: <1417728779.2721.15.camel@perches.com>
On Thu, Dec 04, 2014 at 01:32:59PM -0800, Joe Perches wrote:
> Just fyi.
>
> At least for x86-32, it seems later versions of gcc
> are producing smaller images.
>
> $ size vmlinux.*
> text data bss dec hex filename
> 657725 118496 1189040 1965261 1dfccd vmlinux.4.4
> 633563 118528 1189448 1941539 1da023 vmlinux.4.6
> 633277 118496 1189592 1941365 1d9f75 vmlinux.4.7
> 632299 121120 1192784 1946203 1db25b vmlinux.4.9
I would certainly hope that GCC's -Os gets better over time. However, I
find the increase in data/bss and thus overall size in 4.9 concerning.
Any idea what that comes from?
- Josh Triplett
next prev parent reply other threads:[~2014-12-04 22:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-04 21:32 tinyconfig x86-32 vmlinux sizes by gcc compiler version Joe Perches
2014-12-04 22:25 ` josh [this message]
2014-12-04 22:43 ` Joe Perches
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=20141204222521.GA20091@cloud \
--to=josh@joshtriplett.org \
--cc=joe@perches.com \
--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