From: Kumar Gala <kumar.gala@freescale.com>
To: "Paul Mackerras" <paulus@samba.org>
Cc: linuxppc-dev@ozlabs.org, trini@kernel.crashing.org
Subject: Re: [PATCH] Set cpu explicitly in kernel compiles
Date: Wed, 4 May 2005 08:45:51 -0500 [thread overview]
Message-ID: <3ef0069e8d123c43579a8cc85d20467c@freescale.com> (raw)
In-Reply-To: <17016.29775.224816.691409@cargo.ozlabs.ibm.com>
On May 4, 2005, at 2:05 AM, Paul Mackerras wrote:
> What do people think of this patch?=A0 The motivation for it is that a
> biarch gcc-4.0 will by default tune for POWER4, even for a 32-bit
> compile, meaning that we end up with a lot of nops we don't need.
> This also takes out -mstring.
>
> With this, the text size reduces by about 120k for my normal config
> when compiling with a biarch gcc-4.0.=A0 The text size also reduces
> slightly when compiling with the Debian gcc-3.3.5 (32-bit only, not
> biarch).
What is attributed to this large of a text size change. I've always=20
assumed the -mcpu and -mtune options really only effected code=20
scheduling. This seems really odd since there arent really that many=20
different instructions between the various PPC variants.
- kumar=
next prev parent reply other threads:[~2005-05-04 18:08 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-04 7:05 [PATCH] Set cpu explicitly in kernel compiles Paul Mackerras
2005-05-04 11:28 ` Dan Malek
2005-05-04 15:34 ` Tom Rini
2005-05-04 16:06 ` Chris Friesen
2005-05-04 21:36 ` Paul Mackerras
2005-05-04 23:21 ` Dan Malek
2005-05-05 4:00 ` Paul Mackerras
2005-05-05 4:12 ` Tom Rini
2005-05-05 4:44 ` Paul Mackerras
2005-05-05 4:47 ` Tom Rini
2005-05-05 5:22 ` Paul Mackerras
2005-05-05 12:24 ` Dan Malek
2005-05-05 14:00 ` Kumar Gala
2005-05-05 14:23 ` Tom Rini
2005-05-05 15:12 ` Kumar Gala
2005-05-05 15:27 ` Tom Rini
2005-05-05 16:22 ` Kumar Gala
2005-05-05 16:29 ` Tom Rini
2005-05-06 14:44 ` Segher Boessenkool
2005-05-06 14:53 ` Tom Rini
2005-05-06 15:28 ` Segher Boessenkool
2005-05-06 15:34 ` Tom Rini
2005-05-06 15:47 ` Kumar Gala
2005-05-05 12:12 ` Dan Malek
2005-05-04 13:45 ` Kumar Gala [this message]
2005-05-04 15:28 ` Tom Rini
2005-07-03 17:29 ` Olaf Hering
2005-07-03 18:32 ` Tom Rini
2005-07-05 18:14 ` Olaf Hering
2005-07-05 19:47 ` Tom Rini
2005-07-05 19:54 ` Olaf Hering
2005-07-05 19:58 ` Tom Rini
2005-07-05 20:17 ` Olaf Hering
2005-07-05 20:27 ` Olaf Hering
2005-07-05 21:22 ` Tom Rini
2005-07-06 6:38 ` Olaf Hering
2006-04-02 19:40 ` Olaf Hering
2006-04-06 4:37 ` Paul Mackerras
2006-04-11 18:42 ` Olaf Hering
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=3ef0069e8d123c43579a8cc85d20467c@freescale.com \
--to=kumar.gala@freescale.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.org \
--cc=trini@kernel.crashing.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).