linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Segher Boessenkool <segher@kernel.crashing.org>
To: Akinobu Mita <mita@fixstars.com>
Cc: linuxppc-dev list <linuxppc-dev@ozlabs.org>,
	Paul Mackerras <paulus@samba.org>,
	cbe-oss-dev@ozlabs.org, Arnd Bergmann <arnd@arndb.de>
Subject: Re: [PATCH] force -mno-string option on cell
Date: Fri, 23 Mar 2007 13:56:51 +0100	[thread overview]
Message-ID: <d7a191672b71056daf28a7c93c4e969c@kernel.crashing.org> (raw)
In-Reply-To: <20070323120619.GA7472@localhost.localdomain>

> GCC may generate inline copy loop to handle memcpy() function
> instead of kernel defined memcpy() with -mstring or -Os.
> But this inlined version of memcpy() caused an alignment interrupt
> when copying from SPU local store on PS3.
> (http://ozlabs.org/pipermail/cbe-oss-dev/2007-March/001348.html)
>
> This patch deletes -mstring option on all powerpc and force -mno-string
> option on Cell.

Please split into two patches, the first half (deleting
-mstring) we can all agree on and "the other half".

What your patch does is setting -mno-string for all files
if your kernel is configured to support Cell.  It would be
better to set this option (and all other options needed,
-mno-multiple and -mno-algebraic come to mind, and that last
compiler option doesn't even exist yet) unconditionally on
the few Cell-specific files that are affected, not on the
whole kernel:

	CFLAGS_whatever.o := -msome-flags

It would be even better to not lie to the compiler by
telling it it can use the LS area as normal memory, since
evidently it cannot :-)


Segher

  reply	other threads:[~2007-03-23 12:56 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-22  6:23 [PATCH] powerpc: Always use -mno-string Benjamin Herrenschmidt
2007-03-22 12:06 ` Segher Boessenkool
2007-03-23 12:06   ` [PATCH] force -mno-string option on cell Akinobu Mita
2007-03-23 12:56     ` Segher Boessenkool [this message]
2007-03-23 19:38       ` Benjamin Herrenschmidt
2007-03-24  0:02         ` Segher Boessenkool
2007-03-23 20:46       ` [Cbe-oss-dev] " Arnd Bergmann
2007-03-26 12:00         ` Segher Boessenkool
2007-03-24  3:02       ` Paul Mackerras
2007-03-24 14:46         ` Segher Boessenkool
2007-03-23 13:37     ` Kumar Gala
2007-03-23 16:35       ` Segher Boessenkool
2007-03-23 19:46         ` Benjamin Herrenschmidt
2007-03-24  0:04           ` Segher Boessenkool
2007-03-26  8:54             ` Geert Uytterhoeven
2007-03-26 12:33               ` 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=d7a191672b71056daf28a7c93c4e969c@kernel.crashing.org \
    --to=segher@kernel.crashing.org \
    --cc=arnd@arndb.de \
    --cc=cbe-oss-dev@ozlabs.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=mita@fixstars.com \
    --cc=paulus@samba.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).