summaryrefslogtreecommitdiff
path: root/src/binary-reader.cc
Commit message (Collapse)AuthorAgeFilesLines
* Update testsuite (#2495)Keith Winstein2024-10-301-1/+2
| | | | | The memory64 `table.wast` test has started to depend on function-references and gc (which WABT doesn't support yet), so vendor an older version of the test.
* interp: Handle ref.null exn (#2497)Soni L.2024-10-291-0/+3
|
* wasm-interp: Fix catch handlers correctly (#2483)Soni L.2024-10-071-0/+1
| | | local decl count != local count
* Fix handling of data count without data section (#2432)Soni L.2024-09-231-6/+11
| | | | | | Closes #2436 Fixes #2310 Fixes #2311 Fixes #2431
* Add missing relocation types (and delete a non-existent one) (#2457)SingleAccretion2024-08-291-1/+5
|
* Harden against invalid alignment (#2411)Soni L.2024-08-091-6/+23
|
* Update testsuite and implement table64 (#2418)Sam Clegg2024-05-151-1/+3
| | | | | See https://github.com/WebAssembly/memory64/issues/51 Includes workaround for #2422
* Implement custom section reading/writing (#2284)Diego Frias2023-09-151-5/+35
|
* Flip order of memory indexes on memory.copy (#2294)Keith Winstein2023-09-111-4/+4
| | | | Reflects change in the multi-memory proposal: https://github.com/WebAssembly/multi-memory/pull/29
* Share reading/validation code between elem exprs & other const exprs (#2288)Keith Winstein2023-09-061-18/+7
| | | | | | This continues the work from #1783 and reduces special handling of elem exprs, by treating them the same as other const expressions (init expressions).
* BinaryReader/Writer: roundtrip large memory64 offsets (#2255)Keith Winstein2023-06-201-1/+1
| | | With memory64, the offset becomes a u64.
* memory64: when enabled, check offset range at validation-time (#2253)Keith Winstein2023-06-121-10/+1
| | | | | | | | | | | | | | | | * memory64: when enabled, offset range check is at validation-time Before memory64, the "offset" in a load/store expression was a u32, and we enforced this in the WastParser and BinaryReader. After memory64, the "offset" becomes a u64 syntactically, and the validator checks that it's <= UINT32_MAX for i32 memories. We hadn't been correctly allowing these very large offsets in the text format (even when memory64 was enabled and the memory was i64). (This change also eliminates the "memories" member in the BinaryReader. The BinaryReader no longer needs to keep track of the memories and their types to check well-formedness.)
* binary-reader.cc: detect more malformed modules (#2251)Keith Winstein2023-06-081-27/+23
|
* BinaryReader/BinaryReaderIR: check for missing end markers (#2218)Keith Winstein2023-05-031-1/+8
|
* wasm-objdump: Include function names in "init functions" subsection (#2202)Sam Clegg2023-04-201-3/+3
|
* binary-reader.cc: expand max local count and fix error message (#2173)Keith Winstein2023-03-151-2/+2
| | | | | * binary-reader.cc: expand max local count and fix error message Fixes #1593
* Use C++17's [[fallthrough]]. NFC (#2091)Sam Clegg2023-02-271-1/+1
|
* Fix typo in binary-reader.cc (#2127)Tatsuyuki Kobayashi2023-01-141-4/+4
|
* Use C++17's [[nodiscard]]. NFC (#2090)Sam Clegg2022-12-021-76/+74
|
* Implement Relaxed SIMD proposal (#1994)Marcus Better2022-11-301-0/+20
| | | | | | | | This adds support for the new opcodes from the Relaxed SIMD proposal (https://github.com/WebAssembly/relaxed-simd) behind the "--enable-relaxed-simd" flag. The exception is the f32x4.relaxed_dot_bf16x8_add_f32x4 instruction which is not yet implemented.
* Move headers to include/wabt/ (#1998)Alex Reinking2022-09-281-7/+7
| | | This makes things easier for users and packagers of libwabt.
* Support multi-memory in all memory ops and in apply/resolve-names (#1962)Keith Winstein2022-08-151-94/+129
|
* Continue dumping sections even when one is unknown (#1884)Rafael Fernández López2022-04-211-7/+26
| | | | | | | | | | This is relevant so that when we are dumping a module that contains unknown sections that the current wabt tooling does not understand, we still dump all the sections it understands, skipping (and printing an error) about the unknown sections. Before this change, we would print partial information, stopping at the unknown section, without printing the rest of the sections that wabt could potentially be able to understand.
* Allow binary reader to skip function bodies. NFC (#1871)Sam Clegg2022-03-231-1/+5
| | | | | | | This is purely a performance optimization for wasm-objdump since it doesn't always need to decode function bodies. For a very large wasm file that I was testing this takes the time taken for `wasm-objdump -h` from 8.6s to 1.5s.
* Add initial support for code metadata (#1840)Yuri Iozzelli2022-02-251-0/+58
| | | | | | | | | | | | | | | | | | | | | See https://github.com/WebAssembly/tool-conventions/blob/main/CodeMetadata.md for the specification. In particular this pr implements the following: - Parsing code metadata sections in BinaryReader, providing appropriate callbacks that a BinaryReaderDelegate can implement: - BinaryReaderObjdump: show the sections in a human-readable form - BinaryReaderIr: add code metadata in the IR as expressions - Parsing code metadata annotations in text format, adding them in the IR like the BinaryReaderIR does - Writing the code metadata present in the IR in the proper sections when converting IR to binary - Support in wasm-decompiler for showing code metadata as comments in the pseudo-code All the features have corresponding tests. Support for code metadata is gated through the --enable-code-metadata feature. For reading/writing in the text format, --enable-annotations is also required. Missing features: Support for function-level code metadata (offset 0) Extensive validation in validator.cc (like making sure that all metadata instances are at the same code offset of an instruction)
* Use C++17 string_view (#1826)Sam Clegg2022-02-111-20/+20
| | | | | Now that we have C++17 we don't need our own string_view class anymore. Depends on #1825
* Update testsuite (#1795)Sam Clegg2022-01-101-2/+18
| | | | Remove test/binary/bad-function-missing-end.txt which is now covered upstream: https://github.com/WebAssembly/spec/pull/1405
* Fix type names for function references (#1787)Sam Clegg2021-12-131-1/+1
| | | | | | | | This requires `Type::GetName` to return to be dynamicllay created and return `std::string` rather then a `const char*` As this diff shows this type name is only used in textual output and error messages so should this change should not have a effect of binary parse time or the interpreter.
* wasm-objdump: Fix disassembly output of selectT instruction (#1777)Sam Clegg2021-12-081-3/+7
| | | | Use `LogOpcodeType` rather than LogOpcodeBare` when the select instruction has a type.
* Show tag names in objdump disassembly (#1774)Sam Clegg2021-12-071-0/+1
| | | | | | | | | Tag names are not officially part of the extended-name-section proposal (because it only deals with naming things that are in the spec already). However, I think its reasonable (and useful) to include these names under a speculative subsection ID, on the basis that tags can only exist when exceptions are enabled and that engines should ignore unknown name types.
* Perform init expression validation outside of the binary reader. NFC (#1770)Sam Clegg2021-12-021-94/+29
| | | | | | | | | | | | | | | | Rather than spocial casing them in the reader we now use the same instruction callbacks for instruction that appear in init expressions as instructions that appear in normal functions. The result of this change is the validation of init expressions is pushed further up the stack. For example, objdump will now quite happily dump modules that use arbitrary instructions in thier init expressions even though they are not valid. To me, this makes sense since objdump does not do instruction validation elsewhere. The change is pre-cursor to allowing a wider variety of instruction to be present in init expressions. See https://github.com/WebAssembly/extended-const
* Add multi-memory feature support (#1751)Yuhan Deng2021-11-301-32/+92
|
* Support function references in parameters and results of functions and ↵Dmitry Bezhetskov2021-11-161-1/+10
| | | | blocks. (#1695)
* Remove separate OnEndFunc vs OnEndExpr. (#1756)Sam Clegg2021-11-051-3/+1
| | | | We already have EndFunctionBody, and this extra distinction doesn't seem like it is needed.
* Fix a range of data type warning in gcc (#1702)Hyukwoo Park2021-10-261-2/+1
|
* Add support for target_features section (#1744)Sam Clegg2021-10-191-0/+19
|
* Support for import/export info in dylink section (#1741)Sam Clegg2021-10-191-3/+26
|
* Fix ub access of 0-size vector in data segment (#1725)Ng Zhi An2021-10-121-0/+1
| | | | If the module has no memory, the we try to copy the passive data segment to memories[0], and memories is a size 0 vector, which is UB.
* Support new dylink custom section format (#1707)Sam Clegg2021-09-101-0/+56
| | | | | | | | This section is now based on sub-sections making it more extensible. See also: llvm change: https://reviews.llvm.org/D109595 binaryen change: https://github.com/WebAssembly/binaryen/pull/4141
* Remove ununsed onSymbol callback. NFC (#1708)Sam Clegg2021-09-101-1/+0
| | | | We have the more specific OnFunctionSymbol, OnGlobalSymbol family of callbacks that is used by objdump.
* Begin support for typed function references proposal: added the flag and ↵Dmitry Bezhetskov2021-07-251-0/+5
| | | | supported call_ref (#1691)
* [EH] Remove `unwind` (#1682)Heejin Ahn2021-06-291-6/+0
| | | `unwind` was removed. See WebAssembly/exception-handling#156.
* [EH] Make tag attribute's encoding uint8 (#1681)Heejin Ahn2021-06-291-2/+2
| | | | | | | | | | | This changes the encoding of the `attribute` field, which currently only contains the value `0` denoting this tag is for an exception, from `varuint32` to `uint8`. This field is effectively unused at the moment and reserved for future use, and it is not likely to need `varuint32` even in future. See https://github.com/WebAssembly/exception-handling/pull/162. This does not change any encoded binaries because `0` is encoded in the same way both in `varuint32` and `uint8`.
* [EH] Replace event with tag (#1678)Heejin Ahn2021-06-221-32/+32
| | | | | | | | | | | We recently decided to change 'event' to 'tag', and 'event section' to 'tag section', out of the rationale that the section contains a generalized tag that references a type, which may be used for something other than exceptions, and the name 'event' can be confusing in the web context. See - https://github.com/WebAssembly/exception-handling/issues/159#issuecomment-857910130 - https://github.com/WebAssembly/exception-handling/pull/161
* [Memory64] Support reading/writing limits as 64-bit LEBs (#1664)Wouter van Oortmerssen2021-04-221-5/+16
|
* Memory64: support 64-bit data init-expr (#1656)Wouter van Oortmerssen2021-04-051-11/+11
|
* [simd] Implement store lane (#1647)Ng Zhi An2021-03-221-0/+15
|
* [simd] Implement load lane (#1646)Ng Zhi An2021-03-221-0/+15
| | | | | | | | | This is a new kind of ir/ast node/instruction. It has 3 immediates: memarg align, memarg offset, and lane index. This required new visitor functions in all the places. Drive-by cleanup to share the simd lane parsing logic between shuffle, lane op and this new load lane instructions. This requires rebasing some tests because the error messages are slightly different now.
* [simd] Implement v128.load{32,64}_zero (#1644)Ng Zhi An2021-03-171-0/+11
| | | | This requires a new ir type, and the relevant implementation of virtual mthods in the various visitors.
* [simd] Implement i64x2.extend_{low,high}_i32x4_{s,u} (#1643)Ng Zhi An2021-03-161-0/+4
| | | Unskip and rebase simd_int_to_int_extend.
generated by cgit v1.2.3 (git 2.39.1) at 2025-04-05 20:17:38 +0000