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: [PATCH] powerpc: Always use -mno-string
Date: Thu, 22 Mar 2007 13:06:06 +0100 [thread overview]
Message-ID: <94d8e19d4b061504fcfd08d1ab70cc78@kernel.crashing.org> (raw)
In-Reply-To: <1174544624.10836.24.camel@localhost.localdomain>
> Ok, let's keep load/store multiple, they are only used on 32 bits
> and are actually useful. string instructions are not though.
Sure they are. They are used for 64-bit integers (and
structs) on lots of 32-bit code compiled by GCC. As long
as they are 32-bit aligned, they aren't slow on e.g. PPC750
either.
Just tell GCC what CPU model you want to compile for and
it will try to do the best thing. Don't actively work
against it :-)
Segher
next prev parent reply other threads:[~2007-03-22 12:06 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-22 6:23 [PATCH] powerpc: Always use -mno-string Benjamin Herrenschmidt
2007-03-22 12:06 ` Segher Boessenkool [this message]
2007-03-23 12:06 ` [PATCH] force -mno-string option on cell Akinobu Mita
2007-03-23 12:56 ` Segher Boessenkool
2007-03-23 19:38 ` Benjamin Herrenschmidt
2007-03-24 0:02 ` Segher Boessenkool
2007-03-23 20:46 ` [Cbe-oss-dev] " Arnd Bergmann
2007-03-26 12:00 ` Segher Boessenkool
2007-03-24 3:02 ` Paul Mackerras
2007-03-24 14:46 ` Segher Boessenkool
2007-03-23 13:37 ` Kumar Gala
2007-03-23 16:35 ` Segher Boessenkool
2007-03-23 19:46 ` Benjamin Herrenschmidt
2007-03-24 0:04 ` Segher Boessenkool
2007-03-26 8:54 ` Geert Uytterhoeven
2007-03-26 12:33 ` Segher Boessenkool
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=94d8e19d4b061504fcfd08d1ab70cc78@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 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).