From: Segher Boessenkool <segher@kernel.crashing.org>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Akinobu Mita <mita@fixstars.com>,
Paul Mackerras <paulus@samba.org>,
linuxppc-dev list <linuxppc-dev@ozlabs.org>
Subject: Re: [RFC/PATCH] powerpc: Always use -mno-string & -mno-multiple
Date: Thu, 22 Mar 2007 13:02:42 +0100 [thread overview]
Message-ID: <5fd8e208c5e6c87f852d6a528589dce3@kernel.crashing.org> (raw)
In-Reply-To: <1174543838.10836.21.camel@localhost.localdomain>
> 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.
And they help a lot on many 32-bit CPUs. NAK.
If you tell your GCC to compile for a certain CPU where
these insns would be very slow, GCC will automagically
not generate them, already.
Segher
next prev parent reply other threads:[~2007-03-22 12:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-22 6:10 [RFC/PATCH] powerpc: Always use -mno-string & -mno-multiple Benjamin Herrenschmidt
2007-03-22 12:02 ` Segher Boessenkool [this message]
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=5fd8e208c5e6c87f852d6a528589dce3@kernel.crashing.org \
--to=segher@kernel.crashing.org \
--cc=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.