tradtradcpp0, cpp spec bugs, and use of '|'

[Neil Booth]

Chris G. Demetriou wrote:-

> (1) probably simple to fix: -traditional-cpp is now called an
> unrecognized option, when given to gcc.  (Not quite sure where the
> right place to fix this one would be...)

I'm not sure either.

> (2) when provided with those two options, the driver ends up trying to
> invoke tradtradcpp0.  amusingly, if you add -ftraditional, it tries
> tradtradtradcpp0, etc...  8-)

:-)

> This would seem to be an issue with the use of '|' in the
> trad_capable_cpp spec:
> 
> 	%{traditional|ftraditional|traditional-cpp:trad}cpp0
> 
> from reading the documentation and code, '|' in this case doesn't mean
> "one or the other" it means "for each of those specified, output the
> bits after the colon."  meaning, one of those flags -> trad.  2 ->
> tradtrad.  3-> tradtradtrad.
>
> I don't know if there's an easy way to fix this one at all...

I can't see an easy way; in fact I doubt there is.  Do you have any
ideas, Zack?  These specs get uglier as time goes by...

Neil.