This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug tree-optimization/69615] 0 to limit signed range checks don't always use unsigned compare
- From: "jakub at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Tue, 02 Feb 2016 11:16:18 +0000
- Subject: [Bug tree-optimization/69615] 0 to limit signed range checks don't always use unsigned compare
- Auto-submitted: auto-generated
- References: <bug-69615-4 at http dot gcc dot gnu dot org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69615
--- Comment #4 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
I suppose even that is doable in the reassoc framework, or it could be done in
match.pd just using the recorded value ranges, like richi has handled PR69595,
or both.