From: Arnd Bergmann <arnd@arndb•de>
To: linuxppc-dev@ozlabs•org
Subject: Re: 440 ebony patch seems to have broken 85xx build on powerpc.git
Date: Thu, 24 May 2007 22:21:17 +0200 [thread overview]
Message-ID: <200705242221.17790.arnd@arndb.de> (raw)
In-Reply-To: <1180035543.3360.25.camel@zod.rchland.ibm.com>
On Thursday 24 May 2007, Josh Boyer wrote:
>=20
> > Nothing is telling GCC what CPU to compile for, so it
> > will just use the compiler's default, which very likely
> > is not what you want. =A0For files that will only ever
> > be used on 440, the correct flags are -mcpu=3D440 -Wa,-m440 .
>=20
> We could add that to the per-file flags already, right?
I think it should really use -mcpu=3Dpowerpc on all files.
The problem that Dave saw was the result of using a compiler
that defaults to -mcpu=3D8540, which uses instruction that
don't work on 440.
The common files really need to be built with -mcpu flags that
make the code work on any system if you want to be able
to use just a single boot wrapper binary for all.
Arnd <><
next prev parent reply other threads:[~2007-05-24 20:21 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-24 17:13 440 ebony patch seems to have broken 85xx build on powerpc.git Dave Jiang
2007-05-24 17:37 ` Josh Boyer
2007-05-24 17:43 ` Dave Jiang
2007-05-24 18:02 ` Sergei Shtylyov
2007-05-24 18:09 ` Josh Boyer
2007-05-25 1:27 ` David Gibson
2007-05-24 19:05 ` Segher Boessenkool
2007-05-24 19:39 ` Josh Boyer
2007-05-24 20:18 ` Segher Boessenkool
2007-05-24 20:21 ` Arnd Bergmann [this message]
2007-05-24 20:24 ` Josh Boyer
2007-05-24 21:07 ` Mark A. Greer
2007-05-24 21:16 ` Arnd Bergmann
2007-05-24 22:08 ` Segher Boessenkool
2007-05-24 22:03 ` Segher Boessenkool
2007-05-24 22:02 ` Segher Boessenkool
2007-05-25 1:30 ` David Gibson
2007-05-25 14:01 ` Segher Boessenkool
2007-05-24 22:09 ` Segher Boessenkool
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=200705242221.17790.arnd@arndb.de \
--to=arnd@arndb$(echo .)de \
--cc=linuxppc-dev@ozlabs$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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