summaryrefslogtreecommitdiffstats
path: root/llvm/lib/Object/MachOObjectFile.cpp
diff options
context:
space:
mode:
authorDuncan Sands <baldrick@free.fr>2011-10-26 14:11:18 +0000
committerDuncan Sands <baldrick@free.fr>2011-10-26 14:11:18 +0000
commitdce448c6421ff13df3d8a071aedcd0cefc31c671 (patch)
tree16f7d2622fce5980161b5f63a99d38712f045657 /llvm/lib/Object/MachOObjectFile.cpp
parent4eae54288f1847e5adf97c84c8331380e685037d (diff)
downloadbcm5719-llvm-dce448c6421ff13df3d8a071aedcd0cefc31c671.tar.gz
bcm5719-llvm-dce448c6421ff13df3d8a071aedcd0cefc31c671.zip
Simplify SplitVecRes_UnaryOp by removing all the code that is
trying to legalize the operand types when only the result type is required to be legalized - the type legalization machinery will get round to the operands later if they need legalizing. There can be a point to legalizing operands in parallel with the result: when this saves compile time or results in better code. There was only one case in which this was true: when the operand is also split, so keep the logic for that bit. As a result of this change, additional operand legalization methods may need to be introduced to handle nodes where the result and operand types can differ, like SIGN_EXTEND, but the testsuite doesn't contain any tests where this is the case. In any case, it seems better to require such methods (and die with an assert if they doesn't exist) than to quietly produce wrong code if we forgot to special case the node in SplitVecRes_UnaryOp. llvm-svn: 143026
Diffstat (limited to 'llvm/lib/Object/MachOObjectFile.cpp')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud