[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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

From: Zdenek Dvorak
Subject: Re: changing "configure" to default to "gcc -g -O2 -fwrapv ..."
Date: Sun, 31 Dec 2006 12:10:00 +0100
User-agent: Mutt/1.5.9i


> >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.
> I don't know that area too well, but I think we are already issuing a
> warning if we use -funsafe-loop-optimizations, so it might be possible
> to do the same if we use signed wrapping undefinedness.

not quite; -funsafe-loop-optimizations is not used in scev analysis
itself, only in # of iterations analysis.  At some extra compile-time
cost, you can check whether we use undefinedness of signed overflow
throughout the scev analysis, but there is no way how to avoid duplicate
warnings, and even making the positioning and contents of the warnings
sensible would be nontrivial.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]