loop regression in last 30 hrs.

[Joern Rennecke]

> +FAIL: gcc.c-torture/execute/loop-2b.c execution,  -O2 
> +FAIL: gcc.c-torture/execute/loop-2b.c execution,  -O3 -fomit-frame-pointer 
> +FAIL: gcc.c-torture/execute/loop-2b.c execution,  -O3 -fomit-frame-pointer -fun
> roll-loops 
> +FAIL: gcc.c-torture/execute/loop-2b.c execution,  -O3 -fomit-frame-pointer -fun
> roll-all-loops -finline-functions 
> +FAIL: gcc.c-torture/execute/loop-2b.c execution,  -O3 -g 

loop-2b.c fails or doesn't fail according to random influences.  The
underlying bug got never fixed, so it depends on all kinds of
whacky factors if it gets triggered or not.

>  FAIL: gcc.dg/980312-1.c (test for excess errors)
>  FAIL: gcc.dg/980313-1.c (test for excess errors)
>  FAIL: gcc.dg/990119-1.c execution test

What does gcc.log say about the errors there?