summaryrefslogtreecommitdiffstats
path: root/llvm/test/YAMLParser/duplicate-value-key.former-loader-error.test
diff options
context:
space:
mode:
authorJames Molloy <james.molloy@arm.com>2015-05-16 13:10:45 +0000
committerJames Molloy <james.molloy@arm.com>2015-05-16 13:10:45 +0000
commitb5aa200a33d6b019af43a55ee3b6b2bd951c92e6 (patch)
treec02a0c4877841ee197458af96b37f00e04fd79c2 /llvm/test/YAMLParser/duplicate-value-key.former-loader-error.test
parenta8e1a289397e697a0d63049311b7162669a6b6ce (diff)
downloadbcm5719-llvm-b5aa200a33d6b019af43a55ee3b6b2bd951c92e6.tar.gz
bcm5719-llvm-b5aa200a33d6b019af43a55ee3b6b2bd951c92e6.zip
Reapply r237453 with a fix for the test timeouts.
The test timeouts were due to instcombine fighting itself. Regression test added. Original log message: 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: 237520
Diffstat (limited to 'llvm/test/YAMLParser/duplicate-value-key.former-loader-error.test')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud