This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug tree-optimization/76490] [5/6/7 Regression] when use -O2 -fcheck-founds compiler appears to hang and consumes all memory


https://gcc.gnu.org/bugzilla/show_bug.cgi?id=76490

--- Comment #5 from Richard Biener <rguenth at gcc dot gnu.org> ---
Found new range for isize_3: [1, +INF]
Found new range for isize_20: [1, +INF]
Found new range for isize_5: [1, +INF]
Found new range for _12: [0, 2147483646]
Found new range for _4: [1, 2147483646]
Found new range for isize_3: [1, +INF(OVF)]
Found new range for isize_20: [1, +INF(OVF)]
Found new range for isize_5: [1, +INF(OVF)]
Found new range for _12: [0, +INF(OVF)]
Found new range for _4: [0, +INF]
Found new range for isize_3: [1, +INF]
Found new range for isize_20: [1, +INF]
Found new range for isize_5: [1, +INF]
Found new range for _12: [0, 2147483646]
Found new range for _4: [1, 2147483646]
Found new range for isize_3: [1, +INF(OVF)]
Found new range for isize_20: [1, +INF(OVF)]
...

this happens because intersect_ranges doesn't handle +INF vs. +INF(OVF)
correctly
(operand_equal_p treats them as equal).  I have a patch.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]