llvm-mirror/test/CodeGen/Alpha/zapnot.ll

; Make sure this testcase codegens to the bic instruction
; RUN: llvm-as < %s | llc -march=alpha | grep zapnot


define i16 @foo(i64 %y) zeroext {
entry:
        %tmp.1 = trunc i64 %y to i16         ; <ushort> [#uses=1]
        ret i16 %tmp.1
}
check that casts still use zap llvm-svn: 21283 2005-04-13 13:00:16 +00:00			`; Make sure this testcase codegens to the bic instruction`
For PR1319: Upgrade to use new test harness llvm-svn: 36075 2007-04-15 18:40:57 +00:00			`; RUN: llvm-as < %s \| llc -march=alpha \| grep zapnot`
check that casts still use zap llvm-svn: 21283 2005-04-13 13:00:16 +00:00

For PR1553: Change the keywords for the zext and sext parameter attributes to be zeroext and signext so they don't conflict with the keywords for the instructions of the same name. This gets around the ambiguity. llvm-svn: 40069 2007-07-19 23:13:04 +00:00			`define i16 @foo(i64 %y) zeroext {`
check that casts still use zap llvm-svn: 21283 2005-04-13 13:00:16 +00:00			`entry:`
For PR950: Update the test suite to accommodate the change from signed integer types to signless integer types. The changes were of only a few kinds: 1. Make sure llvm-upgrade is run on the source which does the bulk of the changes automatically. 2. Change things like "grep 'int'" to "grep 'i32'" 3. In several tests bitcasting caused the same name to be reused in the same type plane. These had to be manually fixed. The fix was (generally) to leave the bitcast and provide the instruction with a new name. This should not affect the semantics of the test. In a few cases, the bitcasts were known to be superfluous and irrelevant to the test case so they were removed. 4. One test case uses a bytecode file which needed to be updated to the latest bytecode format. llvm-svn: 32789 2006-12-31 06:02:00 +00:00			`%tmp.1 = trunc i64 %y to i16 ; <ushort> [#uses=1]`
			`ret i16 %tmp.1`
check that casts still use zap llvm-svn: 21283 2005-04-13 13:00:16 +00:00			`}`