https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97721
--- Comment #7 from Jakub Jelinek <jakub at gcc dot gnu.org> --- But TREE_OVERFLOW is meaningful during evaluation, e.g. inside of VRP or when folding some expression. It just doesn't belong into the GIMPLE IL. So I'd say it would be better for ranger when it sees TREE_OVERFLOW constant somewhere in the IL not to set the range to that constant, but to drop_tree_overflow of it.
