From: Josh Boyer <jwboyer@linux.vnet.ibm.com>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: 440 ebony patch seems to have broken 85xx build on powerpc.git
Date: Thu, 24 May 2007 14:39:03 -0500 [thread overview]
Message-ID: <1180035543.3360.25.camel@zod.rchland.ibm.com> (raw)
In-Reply-To: <2ded9f19fbaf49a89ed6e32de87f5828@kernel.crashing.org>
On Thu, 2007-05-24 at 21:05 +0200, Segher Boessenkool wrote:
> > $(obj)/44x.o: BOOTCFLAGS += -Wa,-mbooke
> > $(obj)/ebony.o: BOOTCFLAGS += -Wa,-mbooke
>
> Probably -Wa,-m440 works better. However...
>
> > /opt/montavista/cge/devkit/ppc/85xx/bin/ppc_85xx-gcc -m32
> > -Wp,-MD,arch/powerpc/boot/.ebony.o.d -Wall -Wstrict-prototypes -O2
> > -fomit-frame-pointer -fno-builtin -nostdinc -isystem
> > /opt/montavista/cge/devkit/ppc/85xx/bin/../lib/gcc/powerpc-montavista-
> > linux-gnuspe/4.2.0/include
> > -fPIC -fno-stack-protector -Iarch/powerpc/boot
> > -I/home/djiang/community/git-repos/tmp/ppc-master/arch/powerpc/boot
> > -Wa,-mbooke
> > -c -o arch/powerpc/boot/ebony.o arch/powerpc/boot/ebony.c
>
> 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. For files that will only ever
> be used on 440, the correct flags are -mcpu=440 -Wa,-m440 .
We could add that to the per-file flags already, right?
josh
next prev parent reply other threads:[~2007-05-24 19:40 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 [this message]
2007-05-24 20:18 ` Segher Boessenkool
2007-05-24 20:21 ` Arnd Bergmann
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=1180035543.3360.25.camel@zod.rchland.ibm.com \
--to=jwboyer@linux.vnet.ibm.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=segher@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).