File: global-get-unlowerable.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 (17 lines) | stat: -rw-r--r-- 641 bytes parent folder | download | duplicates (12) 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
 
; RUN: not llc < %s --mtriple=wasm32 2>&1 | FileCheck %s

; Demonstrates a code pattern that could be encountered even with frontend
; restrictions on creating new pointers to globals. In the absence of a better
; fix, the backend should produce a comprehensible message for why it can't
; continue.

; CHECK: LVM ERROR: Encountered an unlowerable load from the wasm_var address space

@g1 = external addrspace(1) global i32
@g2 = external addrspace(1) global i32

define i32 @global_get_phi(i1 zeroext %bool) {
  %sel = select i1 %bool, ptr addrspace(1) @g1, ptr addrspace(1) @g2
  %gval = load i32, ptr addrspace(1) %sel
  ret i32 %gval
}