Bill Wendling a6c3112b1f Situations can arise when you have a function called that returns a 'void', but ... is bitcast to return a floating point value. The result of the instruction may not be used by the program afterwards, and LLVM will happily remove all instructions except the call. But, on some platforms, if a value is returned as a floating point, it may need to be removed from the stack (like x87). Thus, we can't get rid of the bitcast even if there isn't a use of the value. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@51134 91177308-0d34-0410-b5e6-96231b3b80d8		2008-05-14 22:45:20 +00:00
..
Hello	Clean up the use of static and anonymous namespaces. This turned up	2008-05-13 00:00:25 +00:00
Instrumentation	Clean up the use of static and anonymous namespaces. This turned up	2008-05-13 00:00:25 +00:00
IPO	Simplify internalize pass. Add test case.	2008-05-14 20:01:01 +00:00
Scalar	Situations can arise when you have a function called that returns a 'void', but	2008-05-14 22:45:20 +00:00
Utils	Split the loop unroll mechanism logic out into a utility function.	2008-05-14 00:24:14 +00:00
Makefile	remove attribution from lib Makefiles.	2007-12-29 20:09:26 +00:00