Make irange::intersect(wide_int, wide_int) private.
authorAldy Hernandez <aldyh@redhat.com>
Mon, 7 Mar 2022 13:48:58 +0000 (14:48 +0100)
committerAldy Hernandez <aldyh@redhat.com>
Fri, 29 Apr 2022 08:41:59 +0000 (10:41 +0200)
commit71f2928e282eb7863de8426e41c38a90c436d41d
treedb2aca75b24be42a435b32cf72bebead8e8443a4
parent7259481f0ece6283a6e2943448e8d28ffffc40f9
Make irange::intersect(wide_int, wide_int) private.

This method should have been private, and somehow seeped into the API.

Tested and benchmarked on x86-64 Linux.

gcc/ChangeLog:

* gimple-range-cache.h (non_null_ref::adjust_range): Do not use
irange::intersect (wide_int, wide_int).
* gimple-range-fold.cc (adjust_pointer_diff_expr): Same.
(adjust_imagpart_expr): Same.
* value-range.h (irange::intersect (wide_int, wide_int)): Make
private.
gcc/gimple-range-cache.h
gcc/gimple-range-fold.cc
gcc/value-range.h