Hans-Peter Nilsson <h...@bitrange.com> writes:
> On Tue, 28 Aug 2012, Richard Sandiford wrote:
>> Hans-Peter Nilsson <h...@bitrange.com> writes:
>> > On Sun, 26 Aug 2012, Richard Sandiford wrote:
>> >> I'm preparing a patch to turn gcc.target/mips into a torture-like
>> >> testsuite.
>> >
>> > While on the subject of gcc.target/mips and its extensions, it
>> > also doesn't handle a build configured with --with-synci=yes.
>> > (Well, not on the 4.7 branch at least.)
>>
>> What goes wrong?
>
> I don't remember details, but IIRC some synci-related tests go
> wrong for mipsisa32r2el-linux-gnu due to -msynci being the
> default. Don't worry, I've fixed it in the local import. :)
> I though the above would entice you to try it, but I guess I
> need to report better for that to happen. Maybe later.
Trying it now. I suspect it was the problem that Steve hit:
the implicit -msynci is still (deliberately) kept when a lower
architecture is selected.
I'm testing a patch to make the testsuite work out the default
-m{no,}synci, which ought to be enough. The usual rules should
then kick in and force -mno-synci where necessary. Hopefully.
Richard
