------- Comment #8 from mikpe at it dot uu dot se 2010-06-13 17:15 -------
On ARM encode-2.mm fails in part for the same "plain char mangles differently"
reason as on powerpc64, but also due to a backend oddity. Here's how the
string is output in the assembly file on ARM:
.ascii "{?={Vec<double>=ddi}{Vec<float>=ffi}fd{Vec<char>=CC"
.ascii "i}i}\000"
For some reason the ARM backend breaks not very long string literals into
chunks. That's ok in principle because the data is correct in the object file,
but it means that testsuite "scan-assembler" operations become unreliable.
Ideally the test should scan the object file for the string instead, but there
doesn't seem to be a way to do that.
It seems gcc on i686 will also break up long string literals, but it allows for
much much longer strings before doing that.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44518
