From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: Arnd Bergmann <arnd@arndb.de>, Akinobu Mita <mita@fixstars.com>,
linuxppc-dev list <linuxppc-dev@ozlabs.org>,
Paul Mackerras <paulus@samba.org>,
cbe-oss-dev@ozlabs.org
Subject: Re: [PATCH] force -mno-string option on cell
Date: Sat, 24 Mar 2007 06:46:48 +1100 [thread overview]
Message-ID: <1174679208.10836.71.camel@localhost.localdomain> (raw)
In-Reply-To: <b7160f3020aae6e7926b79c14939750c@kernel.crashing.org>
On Fri, 2007-03-23 at 17:35 +0100, Segher Boessenkool wrote:
> > Nack. If GCC is now putting string instructions even if you don't
> > specify -mstring than we also need this for CONFIG_FSL_BOOKE. Please
> > fix that up as well.
>
> In the absence of -mstring and -mno-string options,
> GCC will default to either on or off based on other
> options (CPU model, mostly). This is good behaviour
> since it intends to give you the best code sequences
> for whatever CPU you selected (or for a blended CPU
> model etc).
strings instructions suck, get away with it.
Ben.
next prev parent reply other threads:[~2007-03-23 19:46 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
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 [this message]
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=1174679208.10836.71.camel@localhost.localdomain \
--to=benh@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 \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.