summaryrefslogtreecommitdiffstats
path: root/llvm/lib/VMCore/Use.cpp
diff options
context:
space:
mode:
authorBill Wendling <isanbard@gmail.com>2008-05-14 22:45:20 +0000
committerBill Wendling <isanbard@gmail.com>2008-05-14 22:45:20 +0000
commit3716952f10e8c313184e156b0f095ac614fd6dab (patch)
tree42edbb2217d3b787906ee4ada7f394bf2690e4ac /llvm/lib/VMCore/Use.cpp
parent0424b0e70d227b82c5523c79a861db59343fffd1 (diff)
downloadbcm5719-llvm-3716952f10e8c313184e156b0f095ac614fd6dab.tar.gz
bcm5719-llvm-3716952f10e8c313184e156b0f095ac614fd6dab.zip
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. llvm-svn: 51134
Diffstat (limited to 'llvm/lib/VMCore/Use.cpp')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud