59726668f1
With f3b4f99007, the exclusive source of
truth for whether threads are supported is the -matomics flag.
Accordingly, strip TLS flags when -matomic is not specified, even if
bulk-memory is specified and it would theoretically be supportable.
This allows the backend to compile TLS variables when -mbulk-memory is
enabled but threads are not enabled.
Differential Revision: https://reviews.llvm.org/D125730
32 lines
1023 B
LLVM
32 lines
1023 B
LLVM
; RUN: llc < %s -mattr=-bulk-memory,atomics | FileCheck %s --check-prefixes NO-BULK-MEM
|
|
; RUN: llc < %s -mattr=+bulk-memory,atomics | FileCheck %s --check-prefixes BULK-MEM
|
|
|
|
; Test that the target features section contains -atomics or +atomics
|
|
; for modules that have thread local storage in their source.
|
|
|
|
target triple = "wasm32-unknown-unknown"
|
|
|
|
@foo = internal thread_local global i32 0
|
|
|
|
; -bulk-memory
|
|
; NO-BULK-MEM-LABEL: .custom_section.target_features,"",@
|
|
; NO-BULK-MEM-NEXT: .int8 2
|
|
; NO-BULK-MEM-NEXT: .int8 43
|
|
; NO-BULK-MEM-NEXT: .int8 7
|
|
; NO-BULK-MEM-NEXT: .ascii "atomics"
|
|
; NO-BULK-MEM-NEXT: .int8 45
|
|
; NO-BULK-MEM-NEXT: .int8 10
|
|
; NO-BULK-MEM-NEXT: .ascii "shared-mem"
|
|
; NO-BULK-MEM-NEXT: .bss.foo,"",@
|
|
|
|
; +bulk-memory
|
|
; BULK-MEM-LABEL: .custom_section.target_features,"",@
|
|
; BULK-MEM-NEXT: .int8 2
|
|
; BULK-MEM-NEXT: .int8 43
|
|
; BULK-MEM-NEXT: .int8 7
|
|
; BULK-MEM-NEXT: .ascii "atomics"
|
|
; BULK-MEM-NEXT: .int8 43
|
|
; BULK-MEM-NEXT: .int8 11
|
|
; BULK-MEM-NEXT: .ascii "bulk-memory"
|
|
; BULK-MEM-NEXT: .tbss.foo,"T",@
|