On Thu, Aug 7, 2008 at 9:13 PM, Jack Howarth <[EMAIL PROTECTED]> wrote:
> Eric,
>   Thanks for looking into this. FYI, the problem also occurs in...
>
> FAIL: gcc.dg/torture/fp-int-convert-double.c  -Os  (internal compiler error)
> FAIL: gcc.dg/torture/fp-int-convert-double.c  -Os  (test for excess errors)
> WARNING: gcc.dg/torture/fp-int-convert-double.c  -Os  compilation failed to 
> produce executable
> FAIL: gcc.dg/torture/fp-int-convert-float.c  -Os  (internal compiler error)
> FAIL: gcc.dg/torture/fp-int-convert-float.c  -Os  (test for excess errors)
> WARNING: gcc.dg/torture/fp-int-convert-float.c  -Os  compilation failed to 
> produce executable
> FAIL: gcc.dg/torture/fp-int-convert-timode.c  -Os  (internal compiler error)
> FAIL: gcc.dg/torture/fp-int-convert-timode.c  -Os  (test for excess errors)
> WARNING: gcc.dg/torture/fp-int-convert-timode.c  -Os  compilation failed to 
> produce executable
>
> with the same " in emit_unop_insn, at optabs.c:3806" error message. I don't 
> see
> this failure anywhere in the g++ testsuite though.
>

Looks rather fishy that they're all at -Os. I'd look at things that
went in recently
that would have affected that.

-eric

Reply via email to