summaryrefslogtreecommitdiffstats
path: root/llvm/lib/CodeGen/SelectionDAG/TargetLowering.cpp
diff options
context:
space:
mode:
authorJames Molloy <james.molloy@arm.com>2015-05-20 18:41:25 +0000
committerJames Molloy <james.molloy@arm.com>2015-05-20 18:41:25 +0000
commit2b21a7cf361d9b54459ec6d72847cb4cd5fea1dd (patch)
tree9ab8be94be7d1c53912de291b5b30fbfa75678fd /llvm/lib/CodeGen/SelectionDAG/TargetLowering.cpp
parent60912083310811868759c03777a59e3650a99dfd (diff)
downloadbcm5719-llvm-2b21a7cf361d9b54459ec6d72847cb4cd5fea1dd.tar.gz
bcm5719-llvm-2b21a7cf361d9b54459ec6d72847cb4cd5fea1dd.zip
Reapply r237539 with a fix for the Chromium build.
Make sure if we're truncating a constant that would then be sign extended that the sign extension of the truncated constant is the same as the original constant. > Canonicalize min/max expressions correctly. > > This patch introduces a canonical form for min/max idioms where one operand > is extended or truncated. This often happens when the other operand is a > constant. For example: > > %1 = icmp slt i32 %a, i32 0 > %2 = sext i32 %a to i64 > %3 = select i1 %1, i64 %2, i64 0 > > Would now be canonicalized into: > > %1 = icmp slt i32 %a, i32 0 > %2 = select i1 %1, i32 %a, i32 0 > %3 = sext i32 %2 to i64 > > This builds upon a patch posted by David Majenemer > (https://www.marc.info/?l=llvm-commits&m=143008038714141&w=2). That pass > passively stopped instcombine from ruining canonical patterns. This > patch additionally actively makes instcombine canonicalize too. > > Canonicalization of expressions involving a change in type from int->fp > or fp->int are not yet implemented. llvm-svn: 237821
Diffstat (limited to 'llvm/lib/CodeGen/SelectionDAG/TargetLowering.cpp')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud