From: Ralf Baechle <ralf@linux-mips.org>
To: Manuel Lauss <mano@roarinelk.homelinux.net>
Cc: Linux-MIPS <linux-mips@linux-mips.org>
Subject: Re: [PATCH 2/2] Alchemy: provide cpu feature overrides.
Date: Tue, 23 Dec 2008 17:37:03 +0100 [thread overview]
Message-ID: <20081223163703.GA9952@linux-mips.org> (raw)
In-Reply-To: <20081223172954.06b301cb@scarran.roarinelk.net>
On Tue, Dec 23, 2008 at 05:29:54PM +0100, Manuel Lauss wrote:
> > > Code generated for Alchemy does not use all MIPS32r1 features. Add cpu
> > > feature overrides tailored for Alchemy chips and help GCC create better
> > > code. As a nice sideeffect the size of the resulting kernel is reduced
> > > by a few kilobytes (~200kB for a non-modular db1200 devboard build).
> >
> > The enormous size difference is probably 99% due to atomic and bitops
> > which exist in LL/SC and non-LL/SC versions and without the header gcc
> > will expand the inline function each time. That will hurt, also
> > performance. Also the big size difference suggests that we may want to
> > outline some or all of these functions.
>
> You are of course correct:
>
> text data bss dec hex filename
> 3890074 124400 436528 4451002 43eaba vmlinux
> 3890070 124400 436528 4450998 43eab6 vmlinux+mips32r1
> 3690742 124396 436528 4251666 40e012 vmlinux++llsc
> 3666386 124332 436528 4227246 4080ae vmlinux+++all
Thanks for the numbers. I'm a little surprised that there are only
4 byte difference between the first two variants?
Ralf
next prev parent reply other threads:[~2008-12-23 16:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-22 19:21 [PATCH 1/2] Alchemy: MIPS hazard workarounds are not required Manuel Lauss
2008-12-22 19:21 ` [PATCH 2/2] Alchemy: provide cpu feature overrides Manuel Lauss
2008-12-23 14:39 ` Ralf Baechle
2008-12-23 16:29 ` Manuel Lauss
2008-12-23 16:37 ` Ralf Baechle [this message]
2008-12-23 21:15 ` Manuel Lauss
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=20081223163703.GA9952@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=linux-mips@linux-mips.org \
--cc=mano@roarinelk.homelinux.net \
/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