File: 2005-01-17-CycleInDAG.ll

package info (click to toggle)
llvm-toolchain-17 1%3A17.0.6-22
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid, trixie
  • size: 1,799,624 kB
  • sloc: cpp: 6,428,607; ansic: 1,383,196; asm: 793,408; python: 223,504; objc: 75,364; f90: 60,502; lisp: 33,869; pascal: 15,282; sh: 9,684; perl: 7,453; ml: 4,937; awk: 3,523; makefile: 2,889; javascript: 2,149; xml: 888; fortran: 619; cs: 573
file content (20 lines) | stat: -rw-r--r-- 593 bytes parent folder | download | duplicates (13) 
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 dso_local global i32

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