5 Commits

Author	SHA1	Message	Date
James Molloy	0cbb2a8603	Reapply r233175 and r233183: float2int. ... This re-adds float2int to the tree, after fixing PR23038. It turns out the argument to APSInt() is true-if-unsigned, rather than true-if-signed :(. Added testcase and explanatory comment. llvm-svn: 233370	2015-03-27 10:36:57 +00:00
Nick Lewycky	ffb0864b44	Revert r233175 and r233183 with it. This pulls float2int back out of the tree, due to PR23038. ... llvm-svn: 233350	2015-03-27 02:00:11 +00:00
James Molloy	cb75d92458	Reapply r233062: "float2int": Add a new pass to demote from float to int where possible. ... Now with a fix for PR23008 and extra regression test. llvm-svn: 233175	2015-03-25 10:03:42 +00:00
Hans Wennborg	e42c64551a	Revert r233062 ""float2int": Add a new pass to demote from float to int where possible." ... This caused PR23008, compiles failing with: "Use still stuck around after Def is destroyed: %.sroa.speculated" Also reverting follow-up r233064. llvm-svn: 233105	2015-03-24 20:07:08 +00:00
James Molloy	408df5160c	"float2int": Add a new pass to demote from float to int where possible. ... It is possible to have code that converts from integer to float, performs operations then converts back, and the result is provably the same as if integers were used. This can come from different sources, but the most obvious is a helper function that uses floats but the arguments given at an inlined callsites are integers. This pass considers all integers requiring a bitwidth less than or equal to the bitwidth of the mantissa of a floating point type (23 for floats, 52 for doubles) as exactly representable in floating point. To reduce the risk of harming efficient code, the pass only attempts to perform complete removal of inttofp/fptoint operations, not just move them around. llvm-svn: 233062	2015-03-24 11:15:23 +00:00