From: Segher Boessenkool <segher@kernel.crashing.org>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: linuxppc-dev list <linuxppc-dev@ozlabs.org>,
Paul Mackerras <paulus@samba.org>,
cbe-oss-dev@ozlabs.org, Arnd Bergmann <arnd@arndb.de>,
Akinobu Mita <mita@fixstars.com>
Subject: Re: [PATCH] force -mno-string option on cell
Date: Fri, 23 Mar 2007 17:35:22 +0100 [thread overview]
Message-ID: <b7160f3020aae6e7926b79c14939750c@kernel.crashing.org> (raw)
In-Reply-To: <94FD59E6-B618-4AB2-9BAB-D40A70CC1589@kernel.crashing.org>
> 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).
This isn't new GCC behaviour at all.
If a specific piece of code really needs to be
generated without string insns, you should set the
option in the CFLAGS for that code only.
I don't know what the issue is for FSL BookE; if those
CPUs cannot run string insns in supervisor mode, then
you should indeed have -mno-string globally -- but that
is not the case AFAICS.
Segher
next prev parent reply other threads:[~2007-03-23 16:35 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 [this message]
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=b7160f3020aae6e7926b79c14939750c@kernel.crashing.org \
--to=segher@kernel.crashing.org \
--cc=arnd@arndb.de \
--cc=cbe-oss-dev@ozlabs.org \
--cc=galak@kernel.crashing.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).