Steve Ellcey <sell...@mips.com> writes:
> On Tue, 2012-09-04 at 23:55 +0100, Richard Sandiford wrote:
>> If we do that, then your DRIVER_SELF_SPECS can further have:
>>
>> MIPS_ISA_SYNCI_SPEC
>>
>> where the definition:
>>
>> /* Infer a -msynci setting from a -mips argument, on the assumption that
>> -msynci is desired where possible. */
>> #define MIPS_ISA_SYNCI_SPEC \
>> "%{msynci|mno-synci:;%{mips32r2|mips64r2:-msynci:-mno-synci}}"
>>
>> can go in mips.h. OPTION_DEFAULT_SPECS would then handle synci in just
>> the same way as the other options, without the special SYNCI_SPEC macro.
>
> I am having trouble with this part. The newly built compiler is choking
> on this config spec when building libgcc and I am not sure how to read
> it.
>
> I tried looking in gcc/doc to find a description of the spec syntax but
> I couldn't find where it was documented. I don't know what the
> semicolon does and I have never seen a 3 part spec like
>
> %{mips32r2|mips64r2:-msynci:-mno-synci}
>
> Is this an 'if-then-else' usage?
Yeah, but I typoed, sorry. It should be:
%{mips32r2|mips64r2:-msynci;:-mno-synci}
Richard
