linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Nate Case <ncase@xes-inc.com>
To: Sebastian Andrzej Siewior <sebastian@breakpoint.cc>
Cc: linuxppc-dev@ozlabs.org, ths@linutronix.de
Subject: Re: [PATCH] powerpc: enforce a non-spe kernel build even on broken compilers
Date: Fri, 24 Oct 2008 18:51:17 -0500	[thread overview]
Message-ID: <1224892277.30047.64.camel@localhost.localdomain> (raw)
In-Reply-To: <1224252131.7879.117.camel@localhost.localdomain>

On Fri, 2008-10-17 at 09:02 -0500, Nate Case wrote:
> > With this patch it compiles and boots fine.
> > The option -mabi=no-spe is not required.
> 
> Please don't accept this patch yet.  My past testing showed that
> "-mabi=no-spe" was required for my toolchain.  I'll go back and double
> check though.

OK, I went back and re-tested.

Kernel: 2.6.27
CPU: MPC8572
Toolchain:
    Cross-compiler built using crosstool-ng
    gcc 4.3.1, default target CFLAGS include '-mabi=spe -mspe'
    binutils 2.18.90 snapshot (built with --enable-spe=yes)

Kbuild flags                    Result
------------                    ------
-mno-spe (*)                    FAILED
-mno-spe -mabi=no-spe           FAILED
-mno-spe -mspe=no               OK
-mspe=no                        OK

(*) 2.6.27 default

In the failure case, the kernel would repeatedly dump out "SPE used in
kernel (task=xxxxxxxx, pc=xxxxxxxx)".

I think I was fooled before because I added _both_ "-mspe=no" and
"-mabi=no-spe" to my KBUILD_CFLAGS and saw the problem go away.  Since I
trusted the documentation that -mspe=no and -mno-spe were the same, I
assumed that -mabi=no-spe was the key.

So, I've changed my mind.  I now agree with Sebastian that
"-mabi=no-spe" is not required.  "-mno-spe -mspe=no" is probably the
safe way to go.

-- 
Nate Case <ncase@xes-inc.com>

  parent reply	other threads:[~2008-10-24 23:51 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-01 14:23 [PATCH] powerpc: enforce a non-spe kernel build even on broken compilers Sebastian Siewior
2008-10-14 19:25 ` Nate Case
2008-10-14 22:02   ` Nate Case
2008-10-14 21:23 ` Kumar Gala
2008-10-14 22:35   ` Nate Case
2008-10-14 22:49   ` Sebastian Andrzej Siewior
2008-10-15  8:59     ` Sebastian Andrzej Siewior
2008-10-15 13:25       ` Kumar Gala
2008-10-15 14:43         ` Sebastian Andrzej Siewior
2008-10-15 16:31           ` Kumar Gala
2008-10-17 14:02           ` Nate Case
2008-10-17 15:01             ` Sebastian Andrzej Siewior
2008-10-24 23:51             ` Nate Case [this message]
2008-10-24 23:55               ` Kumar Gala

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=1224892277.30047.64.camel@localhost.localdomain \
    --to=ncase@xes-inc.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=sebastian@breakpoint.cc \
    --cc=ths@linutronix.de \
    /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).