en Copyright 2015 Java http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/test/MC/WebAssembly/data-section.s#9ac5620c [WebAssembly] Rename WasmLimits::Initial to ::Minimum. NFC.This patch renames the "Initial" member of WasmLimits to the name usedin the spec, "Minimum".In the core WebAssembly specification, the Limits data type has onerequired "min" member and one optional "max" member, indicating theminimum required size of the corresponding table or memory, and themaximum size, if any.Although the WebAssembly spec does instantiate locally-defined tablesand memories with the initial size being equal to the minimum size, itcan't impose such a requirement for imports. It doesn't make sense torequire an initial size for a memory import, for example. The compilercan only sensibly express the minimum and maximum sizes.Seehttps://github.com/WebAssembly/js-types/blob/master/proposals/js-types/Overview.md#naming-of-size-limitsfor a related discussion that agrees that the right name of "initial" is"minimum" when querying the type of a table or memory from JavaScript.(Of course it still makes sense for JS to speak in terms of an initialsize when it explicitly instantiates memories and tables.)Differential Revision: https://reviews.llvm.org/D99186 List of files: /llvm-project-15.0.7/llvm/test/MC/WebAssembly/data-section.s Tue, 23 Mar 2021 13:46:32 +0000 Andy Wingo <wingo@igalia.com> http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/test/MC/WebAssembly/data-section.s#8638c897 [WebAssembly] Remove unimplemented-simd target featureNow that the WebAssembly SIMD specification is finalized and engines aregenerally up-to-date, there is no need for a separate target feature for gatingSIMD instructions that engines have not implemented. With this change,v128.const is now enabled by default with the simd128 target feature.Differential Revision: https://reviews.llvm.org/D98457 List of files: /llvm-project-15.0.7/llvm/test/MC/WebAssembly/data-section.s Thu, 18 Mar 2021 17:23:12 +0000 Thomas Lively <tlively@google.com> http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/test/MC/WebAssembly/data-section.s#0d9b17d0 [WebAssembly] fixed wasm64 data segment init exp not 64-bitAs defined in the spec:https://github.com/WebAssembly/memory64/blob/master/proposals/memory64/Overview.mdDifferential Revision: https://reviews.llvm.org/D95651 List of files: /llvm-project-15.0.7/llvm/test/MC/WebAssembly/data-section.s Fri, 29 Jan 2021 00:38:24 +0000 Wouter van Oortmerssen <aardappel@gmail.com> http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/test/MC/WebAssembly/data-section.s#feac819e [MC][WebAssembly] Only emit indirect function table import if neededThe indirect function table, synthesized by the linker, is needed if andonly if there are TABLE_INDEX relocs.Differential Revision: https://reviews.llvm.org/D91637 List of files: /llvm-project-15.0.7/llvm/test/MC/WebAssembly/data-section.s Wed, 25 Nov 2020 16:31:05 +0000 Andy Wingo <wingo@igalia.com> http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/test/MC/WebAssembly/data-section.s#9aa78982 Reland "[lib/Support/YAMLTraits] - Don't print leading zeroes when dumping Hex8/Hex16/Hex32 types." (https://reviews.llvm.org/D90930).This reverts reverting commit fc40a03323a4b265ccbed34a07e281b13c5e8367and fixes LLD (MachO/wasm) tests that failed previously. List of files: /llvm-project-15.0.7/llvm/test/MC/WebAssembly/data-section.s Wed, 18 Nov 2020 08:59:49 +0000 Georgii Rymar <grimar@accesssoftek.com> http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/test/MC/WebAssembly/data-section.s#fc40a033 Revert "[lib/Support/YAMLTraits] - Don't print leading zeroes when dumping Hex8/Hex16/Hex32 types."This reverts commit 65fd17c241e22e1671e81efdb683687369c2feb3.It breaks LLD/MachO tests that seems use obj2yaml the check the output. List of files: /llvm-project-15.0.7/llvm/test/MC/WebAssembly/data-section.s Wed, 18 Nov 2020 08:55:03 +0000 Georgii Rymar <grimar@accesssoftek.com> http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/test/MC/WebAssembly/data-section.s#65fd17c2 [lib/Support/YAMLTraits] - Don't print leading zeroes when dumping Hex8/Hex16/Hex32 types.When we produce an YAML output, we also print leading zeroes currently.An output might look like this:```- Name: .dynsym Type: SHT_DYNSYM Address: 0x0000000000001000 EntSize: 0x0000000000000018```There are probably no reason to print leading zeroes.It just makes harder to read values. This patch stops printing them.The output becomes like:```- Name: .dynsym Type: SHT_DYNSYM Address: 0x1000 EntSize: 0x18```This affects obj2yaml mostly, but also dsymutil and llvm-xray tools output.Differential revision: https://reviews.llvm.org/D90930 List of files: /llvm-project-15.0.7/llvm/test/MC/WebAssembly/data-section.s Fri, 06 Nov 2020 10:39:55 +0000 Georgii Rymar <grimar@accesssoftek.com> http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/test/MC/WebAssembly/data-section.s#388fb67b [WebAssembly] Added .tabletype to asm and multiple table support in obj filesAdds more testing in basic-assembly.s and a new test tables.s.Adds support to yaml reading and writing of tables as well.Differential Revision: https://reviews.llvm.org/D88815 List of files: /llvm-project-15.0.7/llvm/test/MC/WebAssembly/data-section.s Tue, 13 Oct 2020 14:13:10 +0000 Paulo Matos <pmatos@linki.tools> http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/test/MC/WebAssembly/data-section.s#393d0f79 [WebAssembly] Allow multivalue signatures in object filesSummary:Also changes the wasm YAML format to reflect the possibility of havingmultiple return types and to put the returns after the params forconsistency with the binary encoding.Reviewers: aheejin, sbc100Subscribers: dschuff, jgravelle-google, hiraditya, sunfish, arphaman, rupprecht, llvm-commitsTags: #llvmDifferential Revision: https://reviews.llvm.org/D69156llvm-svn: 375283 List of files: /llvm-project-15.0.7/llvm/test/MC/WebAssembly/data-section.s Fri, 18 Oct 2019 20:27:30 +0000 Thomas Lively <tlively@google.com> http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/test/MC/WebAssembly/data-section.s#fef8de66 [WebAssembly] Add DataCount section to object filesSummary:This ensures that object files will continue to validate asWebAssembly modules in the presence of bulk memory operations. Enginesthat don't support bulk memory operations will not recognize theDataCount section and will report validation errors, but that's okbecause object files aren't supposed to be run directly anyway.Reviewers: aheejin, dschuff, sbc100Subscribers: jgravelle-google, hiraditya, sunfish, rupprecht, llvm-commitsTags: #llvmDifferential Revision: https://reviews.llvm.org/D60623llvm-svn: 358315 List of files: /llvm-project-15.0.7/llvm/test/MC/WebAssembly/data-section.s Fri, 12 Apr 2019 22:27:48 +0000 Thomas Lively <tlively@google.com> http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/test/MC/WebAssembly/data-section.s#f3feb6ad [WebAssembly] Add support for data sections in the assembler.Summary:This is quite minimal so far, introduce them with .section,fill them with .int8 or .asciz, end with .sizeReviewers: dschuff, sbc100, aheejinSubscribers: jgravelle-google, sunfish, llvm-commitsTags: #llvmDifferential Revision: https://reviews.llvm.org/D58660llvm-svn: 355321 List of files: /llvm-project-15.0.7/llvm/test/MC/WebAssembly/data-section.s Mon, 04 Mar 2019 17:18:04 +0000 Wouter van Oortmerssen <aardappel@gmail.com>