* gimple-ssa-evrp-analyze.c
(evrp_range_analyzer::extract_range_from_stmt): Always use vr_values::update_value_range so preexisting range info is medged with new range info, even if the new range is VR_VARYING. From-SVN: r255386
This commit is contained in:
parent
178667d2fd
commit
d48f6f3f2d
@ -1,3 +1,10 @@
|
||||
2017-12-04 Jeff Law <law@redhat.com>
|
||||
|
||||
* gimple-ssa-evrp-analyze.c
|
||||
(evrp_range_analyzer::extract_range_from_stmt): Always use
|
||||
vr_values::update_value_range so preexisting range info is
|
||||
medged with new range info, even if the new range is VR_VARYING.
|
||||
|
||||
2017-12-04 Segher Boessenkool <segher@kernel.crashing.org>
|
||||
|
||||
* combine.c: Adjust comment.
|
||||
|
@ -271,8 +271,7 @@ evrp_range_analyzer::record_ranges_from_stmt (gimple *stmt)
|
||||
edge taken_edge;
|
||||
value_range vr = VR_INITIALIZER;
|
||||
vr_values->extract_range_from_stmt (stmt, &taken_edge, &output, &vr);
|
||||
if (output
|
||||
&& (vr.type == VR_RANGE || vr.type == VR_ANTI_RANGE))
|
||||
if (output)
|
||||
{
|
||||
vr_values->update_value_range (output, &vr);
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user