llvm-mirror/test/CodeGen/X86/vec_ctbits.ll

; RUN: llc < %s -march=x86-64

declare <2 x i64> @llvm.cttz.v2i64(<2 x i64>, i1)
declare <2 x i64> @llvm.ctlz.v2i64(<2 x i64>, i1)
declare <2 x i64> @llvm.ctpop.v2i64(<2 x i64>)

define <2 x i64> @footz(<2 x i64> %a) nounwind {
  %c = call <2 x i64> @llvm.cttz.v2i64(<2 x i64> %a, i1 true)
  ret <2 x i64> %c
}
define <2 x i64> @foolz(<2 x i64> %a) nounwind {
  %c = call <2 x i64> @llvm.ctlz.v2i64(<2 x i64> %a, i1 true)
  ret <2 x i64> %c
}
define <2 x i64> @foopop(<2 x i64> %a) nounwind {
  %c = call <2 x i64> @llvm.ctpop.v2i64(<2 x i64> %a)
  ret <2 x i64> %c
}
Eliminate more uses of llvm-as and llvm-dis. llvm-svn: 81290 2009-09-09 01:54:48 +02:00			`; RUN: llc < %s -march=x86-64`
Allow vector integer constants to be created with SelectionDAG::getConstant, in the same way as vector floating-point constants. This allows the legalize expansion code for @llvm.ctpop and friends to be usable with vector types. llvm-svn: 44954 2007-12-12 23:21:26 +01: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 <2 x i64> @llvm.cttz.v2i64(<2 x i64>, i1)`
			`declare <2 x i64> @llvm.ctlz.v2i64(<2 x i64>, i1)`
Allow vector integer constants to be created with SelectionDAG::getConstant, in the same way as vector floating-point constants. This allows the legalize expansion code for @llvm.ctpop and friends to be usable with vector types. llvm-svn: 44954 2007-12-12 23:21:26 +01:00			`declare <2 x i64> @llvm.ctpop.v2i64(<2 x i64>)`

Add nounwind. llvm-svn: 51665 2008-05-29 09:09:24 +02:00			`define <2 x i64> @footz(<2 x i64> %a) nounwind {`
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			`%c = call <2 x i64> @llvm.cttz.v2i64(<2 x i64> %a, i1 true)`
Allow vector integer constants to be created with SelectionDAG::getConstant, in the same way as vector floating-point constants. This allows the legalize expansion code for @llvm.ctpop and friends to be usable with vector types. llvm-svn: 44954 2007-12-12 23:21:26 +01:00			`ret <2 x i64> %c`
			`}`
Add nounwind. llvm-svn: 51665 2008-05-29 09:09:24 +02:00			`define <2 x i64> @foolz(<2 x i64> %a) nounwind {`
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			`%c = call <2 x i64> @llvm.ctlz.v2i64(<2 x i64> %a, i1 true)`
Allow vector integer constants to be created with SelectionDAG::getConstant, in the same way as vector floating-point constants. This allows the legalize expansion code for @llvm.ctpop and friends to be usable with vector types. llvm-svn: 44954 2007-12-12 23:21:26 +01:00			`ret <2 x i64> %c`
			`}`
Add nounwind. llvm-svn: 51665 2008-05-29 09:09:24 +02:00			`define <2 x i64> @foopop(<2 x i64> %a) nounwind {`
Allow vector integer constants to be created with SelectionDAG::getConstant, in the same way as vector floating-point constants. This allows the legalize expansion code for @llvm.ctpop and friends to be usable with vector types. llvm-svn: 44954 2007-12-12 23:21:26 +01:00			`%c = call <2 x i64> @llvm.ctpop.v2i64(<2 x i64> %a)`
			`ret <2 x i64> %c`
			`}`