On 01/12/15 13:01, Jakub Jelinek wrote:
Hi!
On the following testcase we ICE with -Os -Wtype-limits, as
VR_UNDEFINED has NULL vr0->min and vr0->max. From what the code
does I believe the code only means to handle VR_RANGE and not anything else.
Bootstrapped/regtested on x86_64-linux and i686-linux, ok for trunk?
2015-01-12 Jakub Jelinek <ja...@redhat.com>
PR tree-optimization/64563
* tree-vrp.c (vrp_evaluate_conditional): Check for VR_RANGE
instead of != VR_VARYING.
* gcc.dg/pr64563.c: New test.
What about VR_ANTI_RANGE here? I'm pretty sure
vrp_evaluate_conditional's children will use anti-ranges to simplify
conditionals to constants. Though I guess that doesn't really matter
when it comes to this warning because of the minmax testing... Nevermind.
OK for the trunk.
jeff