[Bug tree-optimization/49715] Could do more efficient unsigned-to-float to conversions based on range information

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49715 Richard Guenther changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|

[Bug tree-optimization/49715] Could do more efficient unsigned-to-float to conversions based on range information

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49715 --- Comment #5 from Richard Guenther 2011-07-25 08:30:50 UTC --- Author: rguenth Date: Mon Jul 25 08:30:46 2011 New Revision: 176735 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=176735 Log: 2011-07-25 Richard Guenther PR tree-op

[Bug tree-optimization/49715] Could do more efficient unsigned-to-float to conversions based on range information

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49715 --- Comment #4 from rguenther at suse dot de 2011-07-12 15:21:51 UTC --- On Tue, 12 Jul 2011, sgunderson at bigfoot dot com wrote: > http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49715 > > --- Comment #3 from sgunderson at bigfoot dot com 2011-07

[Bug tree-optimization/49715] Could do more efficient unsigned-to-float to conversions based on range information

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49715 --- Comment #3 from sgunderson at bigfoot dot com 2011-07-12 15:19:51 UTC --- Wow, answer in record time :-) I don't know anything about GCC internals, so I can't comment much on the patch; my only worry here is what would happen if you had a very

[Bug tree-optimization/49715] Could do more efficient unsigned-to-float to conversions based on range information

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49715 Richard Guenther changed: What|Removed |Added Status|NEW |ASSIGNED AssignedTo|unassigned

[Bug tree-optimization/49715] Could do more efficient unsigned-to-float to conversions based on range information

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49715 Richard Guenther changed: What|Removed |Added Status|UNCONFIRMED |NEW Keywords|