LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: David Gibson <david@gibson.dropbear.id.au>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org, Arnd Bergmann <arnd@arndb.de>
Subject: Re: 440 ebony patch seems to have broken 85xx build on powerpc.git
Date: Fri, 25 May 2007 11:30:05 +1000	[thread overview]
Message-ID: <20070525013005.GB11789@localhost.localdomain> (raw)
In-Reply-To: <ab81cfaedb70d6911fcbac9c43f5cf69@kernel.crashing.org>

On Fri, May 25, 2007 at 12:02:44AM +0200, Segher Boessenkool wrote:
> >>> 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?
> >
> > I think it should really use -mcpu=powerpc on all files.
> > The problem that Dave saw was the result of using a compiler
> > that defaults to -mcpu=8540, which uses instruction that
> > don't work on 440.
> 
> No, those options _do_ work on 440, but the -mbooke
> assembler flag disallows isel (since it is an optional
> insn).

But not on 440GP, which is what Ebony is.

> > 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.
> 
> On any system where they can run at all, yes.  It should
> be fine to compile a 440-only file with 440-specific flags.

-- 
David Gibson			| I'll have my music baroque, and my code
david AT gibson.dropbear.id.au	| minimalist, thank you.  NOT _the_ _other_
				| _way_ _around_!
http://www.ozlabs.org/~dgibson

  reply	other threads:[~2007-05-25  1:30 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
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 [this message]
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=20070525013005.GB11789@localhost.localdomain \
    --to=david@gibson.dropbear.id.au \
    --cc=arnd@arndb.de \
    --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