File: 2005-01-17-CycleInDAG.ll

package info (click to toggle)
llvm-toolchain-18 1%3A18.1.8-20
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid
  • size: 1,909,296 kB
  • sloc: cpp: 6,667,975; ansic: 1,440,452; asm: 883,619; python: 230,549; objc: 76,880; f90: 74,238; lisp: 35,989; pascal: 16,571; sh: 10,229; perl: 7,459; ml: 5,047; awk: 3,523; makefile: 2,992; javascript: 2,149; xml: 892; fortran: 649; cs: 573
file content (20 lines) | stat: -rw-r--r-- 593 bytes parent folder | download | duplicates (18) 
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}}
}