From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: In-Reply-To: <94FD59E6-B618-4AB2-9BAB-D40A70CC1589@kernel.crashing.org> References: <1174544624.10836.24.camel@localhost.localdomain> <94d8e19d4b061504fcfd08d1ab70cc78@kernel.crashing.org> <20070323120619.GA7472@localhost.localdomain> <94FD59E6-B618-4AB2-9BAB-D40A70CC1589@kernel.crashing.org> Mime-Version: 1.0 (Apple Message framework v623) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: From: Segher Boessenkool Subject: Re: [PATCH] force -mno-string option on cell Date: Fri, 23 Mar 2007 17:35:22 +0100 To: Kumar Gala Cc: linuxppc-dev list , Paul Mackerras , cbe-oss-dev@ozlabs.org, Arnd Bergmann , Akinobu Mita List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , > 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