File: fast-isel-pr47040.ll

package info (click to toggle)
llvm-toolchain-19 1%3A19.1.7-3~deb12u1
  • links: PTS, VCS
  • area: main
  • in suites: bookworm-proposed-updates
  • size: 1,998,492 kB
  • sloc: cpp: 6,951,680; ansic: 1,486,157; asm: 913,598; python: 232,024; f90: 80,126; objc: 75,281; lisp: 37,276; pascal: 16,990; sh: 10,009; ml: 5,058; perl: 4,724; awk: 3,523; makefile: 3,167; javascript: 2,504; xml: 892; fortran: 664; cs: 573
file content (21 lines) | stat: -rw-r--r-- 838 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
21
 
; RUN: llc < %s -fast-isel -fast-isel-abort=1 -verify-machineinstrs

; Regression test for PR47040, in which an assertion was improperly
; triggered during FastISel's address computation. The issue was that
; an `Address` set to be relative to FrameIndex zero was incorrectly
; considered to have an unset base. When the left hand side of an add
; set the Address to have a FrameIndex base of 0, the right side would
; not detect that the Address base had already been set and could try
; to set the Address to be relative to a register instead, triggering
; an assertion.

target triple = "wasm32-unknown-unknown"

define i32 @foo() {
  %stack_addr = alloca i32
  %stack_i = ptrtoint ptr %stack_addr to i32
  %added = add i32 %stack_i, undef
  %added_addr = inttoptr i32 %added to ptr
  %ret = load i32, ptr %added_addr
  ret i32 %ret
}