From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Subject: Re: [PATCH] force -mno-string option on cell From: Benjamin Herrenschmidt To: Segher Boessenkool In-Reply-To: References: <1174544624.10836.24.camel@localhost.localdomain> <94d8e19d4b061504fcfd08d1ab70cc78@kernel.crashing.org> <20070323120619.GA7472@localhost.localdomain> <94FD59E6-B618-4AB2-9BAB-D40A70CC1589@kernel.crashing.org> Content-Type: text/plain Date: Sat, 24 Mar 2007 06:46:48 +1100 Message-Id: <1174679208.10836.71.camel@localhost.localdomain> Mime-Version: 1.0 Cc: Arnd Bergmann , Akinobu Mita , linuxppc-dev list , Paul Mackerras , cbe-oss-dev@ozlabs.org List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , 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.