maxjhandsome
/
llvm-project
forked from OSchip/llvm-project
1
0
Fork 0
Code Issues Pull Requests Packages Releases Wiki Activity
llvm-project/llvm/test/MC/WebAssembly/reloc-data.ll

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

49 lines
1.6 KiB
LLVM
Raw Normal View History

[llvm-readobj] Change -long-option to --long-option in tests. NFC We use both -long-option and --long-option in tests. Switch to --long-option for consistency. In the "llvm-readelf" mode, -long-option is discouraged as it conflicts with grouped short options and it is not accepted by GNU readelf. While updating the tests, change llvm-readobj -s to llvm-readobj -S to reduce confusion ("s" is --section-headers in llvm-readobj but --symbols in llvm-readelf). llvm-svn: 359649
2019-05-01 13:27:20 +08:00
; RUN: llc -O0 -filetype=obj %s -o - | llvm-readobj -r --expand-relocs | FileCheck %s
[WebAssembly] MC: Use inline triple in test bitcode files This matches the CodeGen tests and makes it a little easy to run these from the command line manually. Differential Revision: https://reviews.llvm.org/D42440 llvm-svn: 323275
2018-01-24 07:03:47 +08:00
[WebAsembly] Update default triple in test files to wasm32-unknown-unkown. Summary: The final -wasm component has been the default for some time now. Subscribers: jfb, dschuff, jgravelle-google, eraman, aheejin, JDevlieghere, sunfish, llvm-commits Differential Revision: https://reviews.llvm.org/D46342 llvm-svn: 332007
2018-05-11 01:49:11 +08:00
target triple = "wasm32-unknown-unknown"
[WebAssembly] Add size of section header to data relocation offsets. Also, add test for data relocations and fix addend to be signed. Subscribers: jfb, dschuff Differential Revision: https://reviews.llvm.org/D32513 llvm-svn: 301690
2017-04-29 05:22:38 +08:00
; foo and bar are external and internal symbols. a and b are pointers
; initialized to these locations offset by 2 and -2 elements respecitively.
[WebAssembly] MC: Use inline triple in test bitcode files This matches the CodeGen tests and makes it a little easy to run these from the command line manually. Differential Revision: https://reviews.llvm.org/D42440 llvm-svn: 323275
2018-01-24 07:03:47 +08:00
[WebAssembly] Add size of section header to data relocation offsets. Also, add test for data relocations and fix addend to be signed. Subscribers: jfb, dschuff Differential Revision: https://reviews.llvm.org/D32513 llvm-svn: 301690
2017-04-29 05:22:38 +08:00
@foo = external global i32, align 4
@bar = global i64 7, align 4
@a = global i32* getelementptr (i32, i32* @foo, i32 2), align 8
@b = global i64* getelementptr (i64, i64* @bar, i64 -2), align 8
[WebAssembly] Use a separate wasm data segment for each global symbol This is stepping stone towards honoring -fdata-sections and letting the assembler decide how many wasm data segments to create. Differential Revision: https://reviews.llvm.org/D37834 llvm-svn: 313313
2017-09-15 07:07:53 +08:00
@c = global [3 x i32*] [i32* @foo, i32* @foo, i32* @foo], align 16
[WebAssembly] Add size of section header to data relocation offsets. Also, add test for data relocations and fix addend to be signed. Subscribers: jfb, dschuff Differential Revision: https://reviews.llvm.org/D32513 llvm-svn: 301690
2017-04-29 05:22:38 +08:00
[WebAssembly] Use a separate wasm data segment for each global symbol This is stepping stone towards honoring -fdata-sections and letting the assembler decide how many wasm data segments to create. Differential Revision: https://reviews.llvm.org/D37834 llvm-svn: 313313
2017-09-15 07:07:53 +08:00
; CHECK: Format: WASM
; CHECK: Relocations [
[WebAssembly] Add DataCount section to object files Summary: This ensures that object files will continue to validate as WebAssembly modules in the presence of bulk memory operations. Engines that don't support bulk memory operations will not recognize the DataCount section and will report validation errors, but that's ok because object files aren't supposed to be run directly anyway. Reviewers: aheejin, dschuff, sbc100 Subscribers: jgravelle-google, hiraditya, sunfish, rupprecht, llvm-commits Tags: #llvm Differential Revision: https://reviews.llvm.org/D60623 llvm-svn: 358315
2019-04-13 06:27:48 +08:00
; CHECK-NEXT: Section (3) DATA {
[WebAssembly] Use a separate wasm data segment for each global symbol This is stepping stone towards honoring -fdata-sections and letting the assembler decide how many wasm data segments to create. Differential Revision: https://reviews.llvm.org/D37834 llvm-svn: 313313
2017-09-15 07:07:53 +08:00
; CHECK-NEXT: Relocation {
[WebAssembly] Rename relocations from R_WEBASSEMBLY_ to R_WASM_ See https://github.com/WebAssembly/tool-conventions/pull/95. This is less typing and IMHO more readable, and it also fits with our naming around the binary format which tends to use the short name. e.g. include/llvm/BinaryFormat/Wasm.h tools/llvm-objdump/WasmDump.cpp etc.. Differential Revision: https://reviews.llvm.org/D57611 llvm-svn: 353062
2019-02-05 01:28:46 +08:00
; CHECK-NEXT: Type: R_WASM_MEMORY_ADDR_I32 (5)
[WebAssembly] Use a separate wasm data segment for each global symbol This is stepping stone towards honoring -fdata-sections and letting the assembler decide how many wasm data segments to create. Differential Revision: https://reviews.llvm.org/D37834 llvm-svn: 313313
2017-09-15 07:07:53 +08:00
; CHECK-NEXT: Offset: 0x13
[WebAssembly] llvm-readobj: display symbols names in relocations Differential Revision: https://reviews.llvm.org/D46296 llvm-svn: 331279
2018-05-02 00:35:16 +08:00
; CHECK-NEXT: Symbol: foo
[WebAssembly] Use a separate wasm data segment for each global symbol This is stepping stone towards honoring -fdata-sections and letting the assembler decide how many wasm data segments to create. Differential Revision: https://reviews.llvm.org/D37834 llvm-svn: 313313
2017-09-15 07:07:53 +08:00
; CHECK-NEXT: Addend: 8
; CHECK-NEXT: }
; CHECK-NEXT: Relocation {
[WebAssembly] Rename relocations from R_WEBASSEMBLY_ to R_WASM_ See https://github.com/WebAssembly/tool-conventions/pull/95. This is less typing and IMHO more readable, and it also fits with our naming around the binary format which tends to use the short name. e.g. include/llvm/BinaryFormat/Wasm.h tools/llvm-objdump/WasmDump.cpp etc.. Differential Revision: https://reviews.llvm.org/D57611 llvm-svn: 353062
2019-02-05 01:28:46 +08:00
; CHECK-NEXT: Type: R_WASM_MEMORY_ADDR_I32 (5)
[WebAssembly] Use a separate wasm data segment for each global symbol This is stepping stone towards honoring -fdata-sections and letting the assembler decide how many wasm data segments to create. Differential Revision: https://reviews.llvm.org/D37834 llvm-svn: 313313
2017-09-15 07:07:53 +08:00
; CHECK-NEXT: Offset: 0x1C
[WebAssembly] llvm-readobj: display symbols names in relocations Differential Revision: https://reviews.llvm.org/D46296 llvm-svn: 331279
2018-05-02 00:35:16 +08:00
; CHECK-NEXT: Symbol: bar
[WebAssembly] Use a separate wasm data segment for each global symbol This is stepping stone towards honoring -fdata-sections and letting the assembler decide how many wasm data segments to create. Differential Revision: https://reviews.llvm.org/D37834 llvm-svn: 313313
2017-09-15 07:07:53 +08:00
; CHECK-NEXT: Addend: -16
; CHECK-NEXT: }
; CHECK-NEXT: Relocation {
[WebAssembly] Rename relocations from R_WEBASSEMBLY_ to R_WASM_ See https://github.com/WebAssembly/tool-conventions/pull/95. This is less typing and IMHO more readable, and it also fits with our naming around the binary format which tends to use the short name. e.g. include/llvm/BinaryFormat/Wasm.h tools/llvm-objdump/WasmDump.cpp etc.. Differential Revision: https://reviews.llvm.org/D57611 llvm-svn: 353062
2019-02-05 01:28:46 +08:00
; CHECK-NEXT: Type: R_WASM_MEMORY_ADDR_I32 (5)
[WebAssembly] Use a separate wasm data segment for each global symbol This is stepping stone towards honoring -fdata-sections and letting the assembler decide how many wasm data segments to create. Differential Revision: https://reviews.llvm.org/D37834 llvm-svn: 313313
2017-09-15 07:07:53 +08:00
; CHECK-NEXT: Offset: 0x25
[WebAssembly] llvm-readobj: display symbols names in relocations Differential Revision: https://reviews.llvm.org/D46296 llvm-svn: 331279
2018-05-02 00:35:16 +08:00
; CHECK-NEXT: Symbol: foo
[WebAssembly] Use a separate wasm data segment for each global symbol This is stepping stone towards honoring -fdata-sections and letting the assembler decide how many wasm data segments to create. Differential Revision: https://reviews.llvm.org/D37834 llvm-svn: 313313
2017-09-15 07:07:53 +08:00
; CHECK-NEXT: Addend: 0
; CHECK-NEXT: }
; CHECK-NEXT: Relocation {
[WebAssembly] Rename relocations from R_WEBASSEMBLY_ to R_WASM_ See https://github.com/WebAssembly/tool-conventions/pull/95. This is less typing and IMHO more readable, and it also fits with our naming around the binary format which tends to use the short name. e.g. include/llvm/BinaryFormat/Wasm.h tools/llvm-objdump/WasmDump.cpp etc.. Differential Revision: https://reviews.llvm.org/D57611 llvm-svn: 353062
2019-02-05 01:28:46 +08:00
; CHECK-NEXT: Type: R_WASM_MEMORY_ADDR_I32 (5)
[WebAssembly] Use a separate wasm data segment for each global symbol This is stepping stone towards honoring -fdata-sections and letting the assembler decide how many wasm data segments to create. Differential Revision: https://reviews.llvm.org/D37834 llvm-svn: 313313
2017-09-15 07:07:53 +08:00
; CHECK-NEXT: Offset: 0x29
[WebAssembly] llvm-readobj: display symbols names in relocations Differential Revision: https://reviews.llvm.org/D46296 llvm-svn: 331279
2018-05-02 00:35:16 +08:00
; CHECK-NEXT: Symbol: foo
[WebAssembly] Use a separate wasm data segment for each global symbol This is stepping stone towards honoring -fdata-sections and letting the assembler decide how many wasm data segments to create. Differential Revision: https://reviews.llvm.org/D37834 llvm-svn: 313313
2017-09-15 07:07:53 +08:00
; CHECK-NEXT: Addend: 0
; CHECK-NEXT: }
; CHECK-NEXT: Relocation {
[WebAssembly] Rename relocations from R_WEBASSEMBLY_ to R_WASM_ See https://github.com/WebAssembly/tool-conventions/pull/95. This is less typing and IMHO more readable, and it also fits with our naming around the binary format which tends to use the short name. e.g. include/llvm/BinaryFormat/Wasm.h tools/llvm-objdump/WasmDump.cpp etc.. Differential Revision: https://reviews.llvm.org/D57611 llvm-svn: 353062
2019-02-05 01:28:46 +08:00
; CHECK-NEXT: Type: R_WASM_MEMORY_ADDR_I32 (5)
[WebAssembly] Use a separate wasm data segment for each global symbol This is stepping stone towards honoring -fdata-sections and letting the assembler decide how many wasm data segments to create. Differential Revision: https://reviews.llvm.org/D37834 llvm-svn: 313313
2017-09-15 07:07:53 +08:00
; CHECK-NEXT: Offset: 0x2D
[WebAssembly] llvm-readobj: display symbols names in relocations Differential Revision: https://reviews.llvm.org/D46296 llvm-svn: 331279
2018-05-02 00:35:16 +08:00
; CHECK-NEXT: Symbol: foo
[WebAssembly] Use a separate wasm data segment for each global symbol This is stepping stone towards honoring -fdata-sections and letting the assembler decide how many wasm data segments to create. Differential Revision: https://reviews.llvm.org/D37834 llvm-svn: 313313
2017-09-15 07:07:53 +08:00
; CHECK-NEXT: Addend: 0
; CHECK-NEXT: }
; CHECK-NEXT: }
; CHECK-NEXT: ]