From: Akinobu Mita <mita@fixstars.com>
To: linuxppc-dev@ozlabs.org
Cc: Arnd Bergmann <arnd@arndb.de>, Paul Mackerras <paulus@samba.org>,
cbe-oss-dev@ozlabs.org
Subject: [patch 2/3] prevent string instructions for FLS_BOOKE
Date: Tue, 10 Apr 2007 20:14:02 +0900 [thread overview]
Message-ID: <20070410111402.GB2957@localhost.localdomain> (raw)
I don't know what is the issue for FSL BookE on -mstring option.
But GCC is now putting string instructions even if you don't
specify -mstring. This patch adds -mno-string option for FLS_BOOKE
and prevents string instruction.
Signed-off-by: Akinobu Mita <mita@fixstars.com>
Index: 2.6-git-ps3/arch/powerpc/Makefile
===================================================================
--- 2.6-git-ps3.orig/arch/powerpc/Makefile
+++ 2.6-git-ps3/arch/powerpc/Makefile
@@ -102,6 +102,10 @@ CFLAGS += $(call cc-option,-mno-altivec)
# kernel considerably.
CFLAGS += $(call cc-option,-funit-at-a-time)
+ifeq ($(CONFIG_FSL_BOOKE),y)
+CFLAGS += -mno-string
+endif
+
ifeq ($(CONFIG_6xx),y)
CFLAGS += -mcpu=powerpc
endif
reply other threads:[~2007-04-10 11:14 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20070410111402.GB2957@localhost.localdomain \
--to=mita@fixstars.com \
--cc=arnd@arndb.de \
--cc=cbe-oss-dev@ozlabs.org \
--cc=linuxppc-dev@ozlabs.org \
--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).