On Sat, Jul 10, 2010 at 03:11:51AM -0400, Joern Rennecke wrote:
> Quoting Jack Howarth :
>
>> Also, I don't seem able to suppress this build failure with...
>
> I think fcode should be assigned some value in the default case instead.
>
>> Is that expected behavior in current gcc trunk?
>
> Strange,
Quoting Jack Howarth :
Also, I don't seem able to suppress this build failure with...
I think fcode should be assigned some value in the default case instead.
Is that expected behavior in current gcc trunk?
Strange, I just bootstrapped r162030 with a small unrelated change on gcc16
(x86_64
