File: schedm7-hazard.ll

package info (click to toggle)
llvm-toolchain-14 1%3A14.0.6-12
  • links: PTS, VCS
  • area: main
  • in suites: bookworm
  • size: 1,496,180 kB
  • sloc: cpp: 5,593,972; ansic: 986,872; asm: 585,869; python: 184,223; objc: 72,530; lisp: 31,119; f90: 27,793; javascript: 9,780; pascal: 9,762; sh: 9,482; perl: 7,468; ml: 5,432; awk: 3,523; makefile: 2,538; xml: 953; cs: 573; fortran: 567
file content (38 lines) | stat: -rw-r--r-- 1,396 bytes parent folder | download | duplicates (7)
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
27
28
29
30
31
32
33
34
35
36
37
38
; NOTE: Assertions have been autogenerated by utils/update_llc_test_checks.py
; RUN: llc < %s -mtriple=thumbv7m-none-eabi -mcpu=cortex-m7 | FileCheck %s --check-prefix=CHECK
; RUN: llc < %s -mtriple=thumbv7m-none-eabi -mcpu=cortex-m7 -arm-data-bank-mask=-1 | FileCheck %s --check-prefix=NOBANK

; This tests the cortex-m7 bank conflict hazard recognizer.
; Normally both loads would be scheduled early (both in the first cycle) due to
; their latency. But will bank conflict to TCM so are scheduled in different
; cycles.

define i32 @test(i32* %x0, i32 %y, i32 %z) {
; CHECK-LABEL: test:
; CHECK:       @ %bb.0: @ %entry
; CHECK-NEXT:    ldr r3, [r0]
; CHECK-NEXT:    subs r1, r3, r1
; CHECK-NEXT:    ldr r0, [r0, #8]
; CHECK-NEXT:    subs r1, r1, r2
; CHECK-NEXT:    adds r1, #1
; CHECK-NEXT:    muls r0, r1, r0
; CHECK-NEXT:    bx lr
; NOBANK-LABEL: test:
; NOBANK:       @ %bb.0: @ %entry
; NOBANK-NEXT:    ldr r3, [r0]
; NOBANK-NEXT:    ldr r0, [r0, #8]
; NOBANK-NEXT:    subs r1, r3, r1
; NOBANK-NEXT:    subs r1, r1, r2
; NOBANK-NEXT:    adds r1, #1
; NOBANK-NEXT:    muls r0, r1, r0
; NOBANK-NEXT:    bx lr
entry:
  %0 = load i32, i32* %x0, align 4
  %mul3 = add nsw i32 %0, 1
  %mul = sub nsw i32 %mul3, %y
  %sub = sub nsw i32 %mul, %z
  %arrayidx1 = getelementptr inbounds i32, i32* %x0, i32 2
  %1 = load i32, i32* %arrayidx1, align 4
  %mul2 = mul nsw i32 %sub, %1
  ret i32 %mul2
}