File: bit-tracking.ll

package info (click to toggle)
llvm-3.0 3.0-10
  • links: PTS, VCS
  • area: main
  • in suites: wheezy
  • size: 75,412 kB
  • sloc: cpp: 468,043; asm: 109,345; ansic: 13,782; sh: 12,935; ml: 4,716; python: 4,351; perl: 2,096; makefile: 1,905; pascal: 1,578; exp: 389; xml: 283; lisp: 187; csh: 117
file content (26 lines) | stat: -rw-r--r-- 1,116 bytes parent folder | download | duplicates (14)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
; This file contains various testcases that require tracking whether bits are
; set or cleared by various instructions.
; RUN: opt < %s -instcombine -instcombine -S |\
; RUN:   not grep %ELIM

; Reduce down to a single XOR
define i32 @test3(i32 %B) {
        %ELIMinc = and i32 %B, 1                ; <i32> [#uses=1]
        %tmp.5 = xor i32 %ELIMinc, 1            ; <i32> [#uses=1]
        %ELIM7 = and i32 %B, -2         ; <i32> [#uses=1]
        %tmp.8 = or i32 %tmp.5, %ELIM7          ; <i32> [#uses=1]
        ret i32 %tmp.8
}

; Finally, a bigger case where we chain things together.  This corresponds to
; incrementing a single-bit bitfield, which should become just an xor.
define i32 @test4(i32 %B) {
        %ELIM3 = shl i32 %B, 31         ; <i32> [#uses=1]
        %ELIM4 = ashr i32 %ELIM3, 31            ; <i32> [#uses=1]
        %inc = add i32 %ELIM4, 1                ; <i32> [#uses=1]
        %ELIM5 = and i32 %inc, 1                ; <i32> [#uses=1]
        %ELIM7 = and i32 %B, -2         ; <i32> [#uses=1]
        %tmp.8 = or i32 %ELIM5, %ELIM7          ; <i32> [#uses=1]
        ret i32 %tmp.8
}