File: 2005-01-17-CycleInDAG.ll

package info (click to toggle)
llvm-toolchain-7 1%3A7.0.1-8%2Bdeb10u2
  • links: PTS, VCS
  • area: main
  • in suites: buster
  • size: 734,616 kB
  • sloc: cpp: 3,776,926; ansic: 633,271; asm: 350,301; python: 142,716; objc: 107,612; sh: 22,626; lisp: 11,056; perl: 7,999; pascal: 6,742; ml: 5,537; awk: 3,536; makefile: 2,557; cs: 2,027; xml: 841; javascript: 518; ruby: 156
file content (20 lines) | stat: -rw-r--r-- 589 bytes parent folder | download | duplicates (8)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
; This testcase was distilled from 132.ijpeg.  Bsaically we cannot fold the
; load into the sub instruction here as it induces a cycle in the dag, which
; is invalid code (there is no correct way to order the instruction).  Check
; that we do not fold the load into the sub.

; RUN: llc < %s -mtriple=i686-- | FileCheck %s

@GLOBAL = external global i32

define i32 @test(i32* %P1, i32* %P2, i32* %P3) nounwind {
; CHECK-LABEL: test:
entry:
  %L = load i32, i32* @GLOBAL
  store i32 12, i32* %P2
  %Y = load i32, i32* %P3
  %Z = sub i32 %Y, %L
  ret i32 %Z
; CHECK-NOT: {{sub.*GLOBAL}}
}