llvm-mirror/test/Transforms/ConstProp/2007-11-23-cttz.ll

; RUN: opt < %s -constprop -S | grep "ret i13 13"
; PR1816
declare i13 @llvm.cttz.i13(i13, i1)

define i13 @test() {
	%X = call i13 @llvm.cttz.i13(i13 0, i1 true)
	ret i13 %X
}
Convert all tests using TCL-style quoting to use shell-style quoting. This was done through the aid of a terrible Perl creation. I will not paste any of the horrors here. Suffice to say, it require multiple staged rounds of replacements, state carried between, and a few nested-construct-parsing hacks that I'm not proud of. It happens, by luck, to be able to deal with all the TCL-quoting patterns in evidence in the LLVM test suite. If anyone is maintaining large out-of-tree test trees, feel free to poke me and I'll send you the steps I used to convert things, as well as answer any painful questions etc. IRC works best for this type of thing I find. Once converted, switch the LLVM lit config to use ShTests the same as Clang. In addition to being able to delete large amounts of Python code from 'lit', this will also simplify the entire test suite and some of lit's architecture. Finally, the test suite runs 33% faster on Linux now. ;] For my 16-hardware-thread (2x 4-core xeon e5520): 36s -> 24s llvm-svn: 159525 2012-07-02 14:47:22 +02:00			`; RUN: opt < %s -constprop -S \| grep "ret i13 13"`
Fix PR1816, by correcting the broken definition of APInt::countTrailingZeros. llvm-svn: 44296 2007-11-23 23:42:31 +01:00			`; PR1816`
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 i13 @llvm.cttz.i13(i13, i1)`
Fix PR1816, by correcting the broken definition of APInt::countTrailingZeros. llvm-svn: 44296 2007-11-23 23:42:31 +01:00
			`define i13 @test() {`
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			`%X = call i13 @llvm.cttz.i13(i13 0, i1 true)`
Fix PR1816, by correcting the broken definition of APInt::countTrailingZeros. llvm-svn: 44296 2007-11-23 23:42:31 +01:00			`ret i13 %X`
			`}`