llvm-mirror/test/CodeGen/Blackfin/2009-08-11-RegScavenger-CSR.ll

; RUN: llc < %s -march=bfin -verify-machineinstrs

declare i64 @llvm.cttz.i64(i64) nounwind readnone

declare i16 @llvm.cttz.i16(i16) nounwind readnone

declare i8 @llvm.cttz.i8(i8) nounwind readnone

define void @cttztest(i8 %A, i16 %B, i32 %C, i64 %D, i8* %AP, i16* %BP, i32* %CP, i64* %DP) {
	%a = call i8 @llvm.cttz.i8(i8 %A)		; <i8> [#uses=1]
	%b = call i16 @llvm.cttz.i16(i16 %B)		; <i16> [#uses=1]
	%d = call i64 @llvm.cttz.i64(i64 %D)		; <i64> [#uses=1]
	store i8 %a, i8* %AP
	store i16 %b, i16* %BP
	store i64 %d, i64* %DP
	ret void
}
Eliminate more uses of llvm-as and llvm-dis. llvm-svn: 81293 2009-09-09 02:09:15 +02:00			`; RUN: llc < %s -march=bfin -verify-machineinstrs`
Rebuild RegScavenger::DistanceMap each time it is needed. The register scavenger maintains a DistanceMap that maps MI pointers to their distance from the top of the current MBB. The DistanceMap is built incrementally in forward() and in bulk in findFirstUse(). It is used by scavengeRegister() to determine which candidate register has the longest unused interval. Unfortunately the DistanceMap contents can become outdated. The first time scavengeRegister() is called, the DistanceMap is filled to cover the MBB. If then instructions are inserted in the MBB (as they always are following scavengeRegister()), the recorded distances are too short. This causes bad behaviour in the included test case where a register use /after/ the current position is ignored because findFirstUse() thinks is is /before/ the current position. A "using an undefined register" assertion follows promptly. The fix is to build a fresh DistanceMap at the top of scavengeRegister(), and discard it after use. This means that DistanceMap is no longer needed as a RegScavenger member variable, and forward() doesn't need to update it. The fix then discloses issue number two in the same test case: The candidate search in scavengeRegister() finds a CSR that has been saved in the prologue, but is currently unused. It would be both inefficient and wrong to spill such a register in the emergency spill slot. In the present case, the emergency slot restore is placed immediately before the normal epilogue restore, leading to a "Redefining a live register" assertion. Fix number two: When scavengerRegister() stumbles upon an unused register that is overwritten later in the MBB, return that register early. It is important to verify that the register is defined later in the MBB, otherwise it might be an unspilled CSR. llvm-svn: 78650 2009-08-11 08:25:12 +02:00
			`declare i64 @llvm.cttz.i64(i64) nounwind readnone`

			`declare i16 @llvm.cttz.i16(i16) nounwind readnone`

			`declare i8 @llvm.cttz.i8(i8) nounwind readnone`

			`define void @cttztest(i8 %A, i16 %B, i32 %C, i64 %D, i8* %AP, i16* %BP, i32* %CP, i64* %DP) {`
			`%a = call i8 @llvm.cttz.i8(i8 %A) ; <i8> [#uses=1]`
			`%b = call i16 @llvm.cttz.i16(i16 %B) ; <i16> [#uses=1]`
			`%d = call i64 @llvm.cttz.i64(i64 %D) ; <i64> [#uses=1]`
			`store i8 %a, i8* %AP`
			`store i16 %b, i16* %BP`
			`store i64 %d, i64* %DP`
			`ret void`
			`}`