Re: changing "configure" to default to "gcc -g -O2 -fwrapv ..."

[Gabriel Dos Reis]

Robert Dewar <address@hidden> writes:

| Gabriel Dos Reis wrote:
| 
| > I have been looking into infer_loop_bounds_from_signedness() called
| > from infer_loop_bounds_from_undefined().
| > At some places, nowrap_type_p() is used but this function operates
| > only on types, so there will be too many false positive there; yet we
| > will miss warning through that case.
| 
| My inclination is to skip the warning for the loop
| induction variable case.

I understand.  

That makes the warning a little bit trickier to implement because some
of the functions that assume "undefined behaviour" don't know whether
they're called for computing ranges just for IV, or for doing general
manipulation outside IV computations.

(Of course, if we had diagnostic context stacks, we could "retire"
some diagnostics emitted for IV before they see the light, but I
suspect that is for another day).

-- Gaby