> > Is there anyway for the optimizers to get at this range information still?
> > Or was range information removed because it is essentially impossible to use
> > it correctly (if so this bug report should be closed as unfixable)?
>
> It was removed because it was impossible to use it correctly.
> I was talking about the rts that get's used if I configure with
> --disable-bootstrap, do a make and then run make check-ada from within the
> gcc/ subdirectory. As far as I understand that rts seems to be built using
> the bootstrap compiler. At least this would explain the difference in the
>
> > we have a disconnect between the redundant checks in the rts and the
> > testcases. If it happens that the non-bootstrapped rts is built by the
> > host compiler(?).
>
> No, that never happens. The rts is always built with the latest (stage3)
> compiler. Otherwise it would not even begin to w
> I guess that nearly all range checks are eliminated and without bootstrapping
> we have a disconnect between the redundant checks in the rts and the
> testcases. If it happens that the non-bootstrapped rts is built by the
> host compiler(?).
No, that never happens. The rts is always built with