All of lore.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Paul Mackerras <paulus@samba.org>
Cc: linuxppc-dev list <linuxppc-dev@ozlabs.org>,
	Akinobu Mita <mita@fixstars.com>
Subject: [RFC/PATCH] powerpc: Always use -mno-string & -mno-multiple
Date: Thu, 22 Mar 2007 17:10:38 +1100	[thread overview]
Message-ID: <1174543838.10836.21.camel@localhost.localdomain> (raw)

powerpc: Always use -mno-string and -mno-multiple

The string and multiple load/store instructions are causing more
damage than help on a lot of processors where they are microcoded
and are generally no good for the kernel to use. Let's make sure
we don't emit them on any powerpc variant.

Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
---

Is that actually true ? What about 601 ? 4xx ? Do we want to keep
generating those for space on embedded processors where they actually
work (if they do) ?

Index: linux-cell/arch/powerpc/Makefile
===================================================================
--- linux-cell.orig/arch/powerpc/Makefile	2007-03-22 17:02:42.000000000 +1100
+++ linux-cell/arch/powerpc/Makefile	2007-03-22 17:05:23.000000000 +1100
@@ -102,9 +102,9 @@ CFLAGS += $(call cc-option,-mno-altivec)
 # kernel considerably.
 CFLAGS += $(call cc-option,-funit-at-a-time)
 
-ifndef CONFIG_FSL_BOOKE
-CFLAGS		+= -mstring
-endif
+# Never use string and multiple load/store instructions as they are
+# often slow when they are implemented at all
+CFLAGS		+= -mno-string -mno-multiple
 
 ifeq ($(CONFIG_6xx),y)
 CFLAGS		+= -mcpu=powerpc

             reply	other threads:[~2007-03-22  6:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-22  6:10 Benjamin Herrenschmidt [this message]
2007-03-22 12:02 ` [RFC/PATCH] powerpc: Always use -mno-string & -mno-multiple Segher Boessenkool
2007-03-22 12:06   ` Benjamin Herrenschmidt

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=1174543838.10836.21.camel@localhost.localdomain \
    --to=benh@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 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.