a8ec6e8788
While external globals can be unsized, I don't think an unsized initializer makes sense. It seems like the backend currently ends up treating this as a zero-size global. If people want that behavior, they should declare it as such.
32 lines
1.3 KiB
LLVM
32 lines
1.3 KiB
LLVM
; RUN: not opt -S -passes=verify < %s 2>&1 | FileCheck %s
|
|
|
|
;; Global variables cannot be scalable vectors, since we don't
|
|
;; know the size at compile time.
|
|
|
|
; CHECK: Globals cannot contain scalable types
|
|
; CHECK-NEXT: ptr @ScalableVecGlobal
|
|
@ScalableVecGlobal = global <vscale x 4 x i32> zeroinitializer
|
|
|
|
; CHECK-NEXT: Globals cannot contain scalable types
|
|
; CHECK-NEXT: ptr @ScalableVecArrayGlobal
|
|
@ScalableVecArrayGlobal = global [ 8 x <vscale x 4 x i32> ] zeroinitializer
|
|
|
|
; CHECK-NEXT: Globals cannot contain scalable types
|
|
; CHECK-NEXT: ptr @ScalableVecStructGlobal
|
|
@ScalableVecStructGlobal = external global { i32, <vscale x 4 x i32> }
|
|
|
|
; CHECK-NEXT: Globals cannot contain scalable types
|
|
; CHECK-NEXT: ptr @StructTestGlobal
|
|
%struct.test = type { <vscale x 1 x double>, <vscale x 1 x double> }
|
|
@StructTestGlobal = global %struct.test zeroinitializer
|
|
|
|
; CHECK-NEXT: Globals cannot contain scalable types
|
|
; CHECK-NEXT: ptr @StructArrayTestGlobal
|
|
%struct.array.test = type { [2 x <vscale x 1 x double>] }
|
|
@StructArrayTestGlobal = external global %struct.array.test
|
|
|
|
; CHECK-NEXT: Globals cannot contain scalable types
|
|
; CHECK-NEXT: ptr @StructTargetTestGlobal
|
|
%struct.target.test = type { target("aarch64.svcount"), target("aarch64.svcount") }
|
|
@StructTargetTestGlobal = external global %struct.target.test
|