File: global-set-unlowerable.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 (17 lines) | stat: -rw-r--r-- 633 bytes parent folder | download | duplicates (14) 
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 store to the wasm_var address space

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

define void @global_set_phi(i1 zeroext %bool) {
  %sel = select i1 %bool, ptr addrspace(1) @g1, ptr addrspace(1) @g2
  store i32 100, ptr addrspace(1) %sel
  ret void
}