Summary: Linker testing was sad at seeing an unresolved external symbol. For now don't do that: it's valid but we're not playing with multi-file linking yet, and the LLVM tests are used as hacky sanity tests for single-file linking (the GCC torture tests are much better for this purpose). Another solution would be to use '.extern' to make the intent explicit (don't simple-file link this, there's an unresolved symbol), some assemblers use '.extern' while others ignore it, so we wouldn't really be inventing anything new.
Reviewers: sunfish, kripken
Subscribers: jfb, llvm-commits, dschuff
Differential Revision: http://reviews.llvm.org/D15753
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@256353
91177308-0d34-0410-b5e6-
96231b3b80d8
target datalayout = "e-p:32:32-i64:64-n32:64-S128"
target triple = "wasm32-unknown-unknown"
-@x = external global [0 x i32]
+; FIXME: make this 'external' and make sure it still works. WebAssembly
+; currently only supports linking single files, so 'external' makes
+; little sense.
+@x = global [0 x i32] zeroinitializer
@y = global [50 x i32] zeroinitializer
; Test basic constant offsets of both defined and external symbols.