[Bug middle-end/56924] Folding of checks into a range check should check upper boundary

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56924 Andrew Pinski changed: What|Removed |Added Assignee|unassigned at gcc dot gnu.org |pinskia at gcc dot gnu.org

[Bug middle-end/56924] Folding of checks into a range check should check upper boundary

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56924 --- Comment #3 from Joshua Conner josh.m.conner at gmail dot com --- It appears that gcc has a different approach now, which has its own advantages and disadvantages. Specifically, when I compile this same example I'm now seeing an initial tree

[Bug middle-end/56924] Folding of checks into a range check should check upper boundary

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56924 --- Comment #2 from Ramana Radhakrishnan ramana at gcc dot gnu.org --- trunk and FSF 4.9.0 currently generates on ARM. and r0, r0, #224 cmp r0, #224 bxnelr b bar which looks way better than

[Bug middle-end/56924] Folding of checks into a range check should check upper boundary

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56924 Richard Biener rguenth at gcc dot gnu.org changed: What|Removed |Added Keywords|