aboutsummaryrefslogtreecommitdiff
path: root/gcc
diff options
context:
space:
mode:
authorAldy Hernandez <aldyh@redhat.com>2018-11-09 09:52:53 +0000
committerAldy Hernandez <aldyh@gcc.gnu.org>2018-11-09 09:52:53 +0000
commit6e40dcaedba8763b465f9d73928209d0fd8a0e86 (patch)
treea98155d9625faa855c662fb5e9efc3fd9ffc7806 /gcc
parent5756b6a8b5e309e84ed8f536672aa3a389c3185a (diff)
downloadgcc-6e40dcaedba8763b465f9d73928209d0fd8a0e86.zip
gcc-6e40dcaedba8763b465f9d73928209d0fd8a0e86.tar.gz
gcc-6e40dcaedba8763b465f9d73928209d0fd8a0e86.tar.bz2
* tree-vrp.c (may_contain_p): Do not access m_min/m_max directly.
From-SVN: r265954
Diffstat (limited to 'gcc')
-rw-r--r--gcc/ChangeLog4
-rw-r--r--gcc/tree-vrp.c4
2 files changed, 6 insertions, 2 deletions
diff --git a/gcc/ChangeLog b/gcc/ChangeLog
index c84b0fd..0d4ab1b 100644
--- a/gcc/ChangeLog
+++ b/gcc/ChangeLog
@@ -1,5 +1,9 @@
2018-11-08 Aldy Hernandez <aldyh@redhat.com>
+ * tree-vrp.c (may_contain_p): Do not access m_min/m_max directly.
+
+2018-11-08 Aldy Hernandez <aldyh@redhat.com>
+
* vr-values.c (vr_values::get_value_range): Use value_range API
instead of piecing together ranges.
(vr_values::update_value_range): Same.
diff --git a/gcc/tree-vrp.c b/gcc/tree-vrp.c
index e45d788..6df749c 100644
--- a/gcc/tree-vrp.c
+++ b/gcc/tree-vrp.c
@@ -250,10 +250,10 @@ value_range::may_contain_p (tree val) const
if (m_kind == VR_ANTI_RANGE)
{
- int res = value_inside_range (val, m_min, m_max);
+ int res = value_inside_range (val, min (), max ());
return res == 0 || res == -2;
}
- return value_inside_range (val, m_min, m_max) != 0;
+ return value_inside_range (val, min (), max ()) != 0;
}
void