RPCS3/llvm-mirror
1
0
Fork 0
mirror of https://github.com/RPCS3/llvm-mirror.git synced 2024-10-31 07:52:55 +01:00
Code Issues Projects Releases Wiki Activity
6c1db18560
llvm-mirror/test/CodeGen/PowerPC/cttz.ll

14 lines
316 B
LLVM
Raw Normal View History

Add testcase for legalizing ISD::CTTZ efficiently. On PPC, ctlz(int) is now codegen'd as this: addi r2, r3, -1 andc r2, r2, r3 cntlzw r2, r2 subfic r3, r2, 32 blr llvm-svn: 21881
2005-05-12 01:45:54 +02:00
; Make sure this testcase does not use ctpop
Fix PowerPC/cttz.ll to specify a cpu (and use FileCheck) llvm-svn: 178472
2013-04-01 18:31:56 +02:00
; RUN: llc < %s -march=ppc32 -mcpu=g5 | FileCheck %s
Add testcase for legalizing ISD::CTTZ efficiently. On PPC, ctlz(int) is now codegen'd as this: addi r2, r3, -1 andc r2, r2, r3 cntlzw r2, r2 subfic r3, r2, 32 blr llvm-svn: 21881
2005-05-12 01:45:54 +02:00
Manually upgrade the test suite to specify the flag to cttz and ctlz. I followed three heuristics for deciding whether to set 'true' or 'false': - Everything target independent got 'true' as that is the expected common output of the GCC builtins. - If the target arch only has one way of implementing this operation, set the flag in the way that exercises the most of codegen. For most architectures this is also the likely path from a GCC builtin, with 'true' being set. It will (eventually) require lowering away that difference, and then lowering to the architecture's operation. - Otherwise, set the flag differently dependending on which target operation should be tested. Let me know if anyone has any issue with this pattern or would like specific tests of another form. This should allow the x86 codegen to just iteratively improve as I teach the backend how to differentiate between the two forms, and everything else should remain exactly the same. llvm-svn: 146370
2011-12-12 12:59:10 +01:00
declare i32 @llvm.cttz.i32(i32, i1)
Add testcase for legalizing ISD::CTTZ efficiently. On PPC, ctlz(int) is now codegen'd as this: addi r2, r3, -1 andc r2, r2, r3 cntlzw r2, r2 subfic r3, r2, 32 blr llvm-svn: 21881
2005-05-12 01:45:54 +02:00
Remove llvm-upgrade and update tests. llvm-svn: 47325
2008-02-19 09:07:33 +01:00
define i32 @bar(i32 %x) {
Add testcase for legalizing ISD::CTTZ efficiently. On PPC, ctlz(int) is now codegen'd as this: addi r2, r3, -1 andc r2, r2, r3 cntlzw r2, r2 subfic r3, r2, 32 blr llvm-svn: 21881
2005-05-12 01:45:54 +02:00
entry:
Fix PowerPC/cttz.ll to specify a cpu (and use FileCheck) llvm-svn: 178472
2013-04-01 18:31:56 +02:00
; CHECK: @bar
; CHECK: cntlzw
Manually upgrade the test suite to specify the flag to cttz and ctlz. I followed three heuristics for deciding whether to set 'true' or 'false': - Everything target independent got 'true' as that is the expected common output of the GCC builtins. - If the target arch only has one way of implementing this operation, set the flag in the way that exercises the most of codegen. For most architectures this is also the likely path from a GCC builtin, with 'true' being set. It will (eventually) require lowering away that difference, and then lowering to the architecture's operation. - Otherwise, set the flag differently dependending on which target operation should be tested. Let me know if anyone has any issue with this pattern or would like specific tests of another form. This should allow the x86 codegen to just iteratively improve as I teach the backend how to differentiate between the two forms, and everything else should remain exactly the same. llvm-svn: 146370
2011-12-12 12:59:10 +01:00
%tmp.1 = call i32 @llvm.cttz.i32( i32 %x, i1 true ) ; <i32> [#uses=1]
Remove llvm-upgrade and update tests. llvm-svn: 47325
2008-02-19 09:07:33 +01:00
ret i32 %tmp.1
Add testcase for legalizing ISD::CTTZ efficiently. On PPC, ctlz(int) is now codegen'd as this: addi r2, r3, -1 andc r2, r2, r3 cntlzw r2, r2 subfic r3, r2, 32 blr llvm-svn: 21881
2005-05-12 01:45:54 +02:00
}
Remove llvm-upgrade and update tests. llvm-svn: 47325
2008-02-19 09:07:33 +01:00
Reference in New Issue Copy Permalink