From: "Steven J. Hill" <Steven.Hill@imgtec.com>
To: Ralf Baechle <ralf@linux-mips.org>
Cc: <linux-mips@linux-mips.org>
Subject: Re: [PATCH] MIPS: Reduce code size for MIPS32R2 platforms.
Date: Thu, 27 Jun 2013 11:10:09 -0500 [thread overview]
Message-ID: <51CC63E1.3080407@imgtec.com> (raw)
In-Reply-To: <20130627155816.GF10727@linux-mips.org>
On 06/27/2013 10:58 AM, Ralf Baechle wrote:
> On Fri, Dec 07, 2012 at 04:09:46PM +0100, Ralf Baechle wrote:
>
> It's a while already - but I haven't forgotten about this little optimization.
>
[...]
>
> Using a quick hack (not in below patch) I reduced CPU support to just a
> single type. Then not only code for the other 2 variants is dropped by
> the compiler but also dead code elimination can discard ifs and switches
> leaving a highly customized, smaller and faster kernel. The best of it
> is that it doesn't even rely on LTO, just a decent optimizer of a per-file
> compiler. Patch for your enjoyment below.
>
> I've done my testing with plain old boring gcc 4.7 btw.
>
Much appreciated. I will test it out here and get back to you. Thanks.
Steve
WARNING: multiple messages have this Message-ID (diff)
From: "Steven J. Hill" <Steven.Hill@imgtec.com>
To: Ralf Baechle <ralf@linux-mips.org>
Cc: linux-mips@linux-mips.org
Subject: Re: [PATCH] MIPS: Reduce code size for MIPS32R2 platforms.
Date: Thu, 27 Jun 2013 11:10:09 -0500 [thread overview]
Message-ID: <51CC63E1.3080407@imgtec.com> (raw)
Message-ID: <20130627161009.K2-_7mRCyR9W66ODKLSJP9s7nwj5xU4Nq2mbEfz1qDs@z> (raw)
In-Reply-To: <20130627155816.GF10727@linux-mips.org>
On 06/27/2013 10:58 AM, Ralf Baechle wrote:
> On Fri, Dec 07, 2012 at 04:09:46PM +0100, Ralf Baechle wrote:
>
> It's a while already - but I haven't forgotten about this little optimization.
>
[...]
>
> Using a quick hack (not in below patch) I reduced CPU support to just a
> single type. Then not only code for the other 2 variants is dropped by
> the compiler but also dead code elimination can discard ifs and switches
> leaving a highly customized, smaller and faster kernel. The best of it
> is that it doesn't even rely on LTO, just a decent optimizer of a per-file
> compiler. Patch for your enjoyment below.
>
> I've done my testing with plain old boring gcc 4.7 btw.
>
Much appreciated. I will test it out here and get back to you. Thanks.
Steve
next prev parent reply other threads:[~2013-06-27 16:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-07 5:14 [PATCH] MIPS: Reduce code size for MIPS32R2 platforms Steven J. Hill
2012-12-07 15:09 ` Ralf Baechle
2013-06-27 15:58 ` Ralf Baechle
2013-06-27 16:10 ` Steven J. Hill [this message]
2013-06-27 16:10 ` Steven J. Hill
2013-09-17 8:25 ` Ralf Baechle
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=51CC63E1.3080407@imgtec.com \
--to=steven.hill@imgtec.com \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.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