Followup to #104926. We ran into issues on the emscripten waterfall where relocation against `__dso_handle` were being reported as errors even though `-r/--relocatable` was being used to generate object file output rather than executable output.
44 lines
1.5 KiB
ArmAsm
44 lines
1.5 KiB
ArmAsm
# RUN: llvm-mc -filetype=obj -triple=wasm64-unknown-unknown -o %t.o %s
|
|
|
|
# RUN: not wasm-ld -mwasm64 --experimental-pic -shared %t.o -o /dev/null 2>&1 | \
|
|
# RUN: FileCheck %s
|
|
|
|
# RUN: not wasm-ld -mwasm64 --experimental-pic -shared %t.o -o /dev/null --unresolved-symbols=report-all 2>&1 | \
|
|
# RUN: FileCheck %s
|
|
|
|
# RUN: not wasm-ld -mwasm64 --experimental-pic -shared %t.o -o /dev/null --warn-unresolved-symbols 2>&1 | \
|
|
# RUN: FileCheck %s
|
|
|
|
# RUN: not wasm-ld -mwasm64 --experimental-pic -shared %t.o -o /dev/null --unresolved-symbols=ignore-all 2>&1 | \
|
|
# RUN: FileCheck %s
|
|
|
|
# RUN: not wasm-ld -mwasm64 --experimental-pic -shared %t.o -o /dev/null --unresolved-symbols=import-dynamic 2>&1 | \
|
|
# RUN: FileCheck %s
|
|
|
|
## These errors should not be reported under -r/--relocation (i.e. when
|
|
## generating an object file)
|
|
# RUN: wasm-ld -mwasm64 --experimental-pic -r %t.o -o /dev/null
|
|
|
|
.functype external_func () -> ()
|
|
|
|
use_undefined_function:
|
|
.functype use_undefined_function () -> ()
|
|
i64.const external_func@TBREL
|
|
# CHECK: error: {{.*}}.o: relocation R_WASM_TABLE_INDEX_REL_SLEB64 is not supported against an undefined symbol `external_func`
|
|
drop
|
|
end_function
|
|
|
|
use_undefined_data:
|
|
.functype use_undefined_data () -> ()
|
|
i64.const external_data@MBREL
|
|
# CHECK: error: {{.*}}.o: relocation R_WASM_MEMORY_ADDR_REL_SLEB64 is not supported against an undefined symbol `external_data`
|
|
drop
|
|
end_function
|
|
|
|
.globl _start
|
|
_start:
|
|
.functype _start () -> ()
|
|
call use_undefined_function
|
|
call use_undefined_data
|
|
end_function
|