[Cbe-oss-dev] [PATCH] force -mno-string option on cell

Segher Boessenkool segher at kernel.crashing.org
Sat Mar 24 11:02:33 EST 2007

> It's fair enough to use -mno-string overall.

> If the kernel is going to
> run on cell, performance will suck with string instructions.


> In fact,
> I'm not sure they are worth having on anything anyway.

We'll have to disagree here.  String insns _are_ useful
on many CPUs.

Either way, even if string insns would suck on every
CPU -- this shouldn't be handled in the kernel Makefiles,
convince the GCC people instead.  If there are no special
considerations why certain insns would be inappropriate
for a certain specific piece of code, you'll just have
to trust the compiler's insn selection.  That's just the
same as for any other isns patterns.

If there are such considerations, add the flags you need
for that source file, and that source file only.

If you don't compile targeting a specific CPU, and GCC's
choices suck on the hardware you actually run on, select
a different cost model.  Or, again, convince the GCC people
to make some changes.


More information about the cbe-oss-dev mailing list