issue_owner_repo listlengths 2 2 | issue_body stringlengths 0 261k β | issue_title stringlengths 1 925 | issue_comments_url stringlengths 56 81 | issue_comments_count int64 0 2.5k | issue_created_at stringlengths 20 20 | issue_updated_at stringlengths 20 20 | issue_html_url stringlengths 37 62 | issue_github_id int64 387k 2.91B | issue_number int64 1 131k |
|---|---|---|---|---|---|---|---|---|---|
[
"WebAssembly",
"wabt"
] | ### Environment
```
OS : Linux ubuntu 5.15.0-46-generic #49~20.04.1-Ubuntu SMP Thu Aug 4 19:15:44 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
Commit : 3054d61f703d609995798f872fc86b462617c294
Version : 1.0.29
Build : make clang-debug-asan
```
### Proof of concept
poc_wasm-validate.wasm
[poc_wasm-validate... | Assertion `enum_ == Enum::Reference' failed at wasm-validate | https://api.github.com/repos/WebAssembly/wabt/issues/1987/comments | 1 | 2022-09-05T13:01:21Z | 2022-09-17T23:30:37Z | https://github.com/WebAssembly/wabt/issues/1987 | 1,361,925,343 | 1,987 |
[
"WebAssembly",
"wabt"
] | ### Environment
```
OS : Linux ubuntu 5.15.0-46-generic #49~20.04.1-Ubuntu SMP Thu Aug 4 19:15:44 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
Commit : 3054d61f703d609995798f872fc86b462617c294
Version : 1.0.29
Build : make clang-debug-asan
```
### Proof of concept
poc_wasm2wat.wasm
[poc_wasm2wat.wasm.zip]... | Assertion `enum_ == Enum::Reference' failed at wasm2wat | https://api.github.com/repos/WebAssembly/wabt/issues/1986/comments | 1 | 2022-09-05T13:00:04Z | 2022-09-17T23:28:33Z | https://github.com/WebAssembly/wabt/issues/1986 | 1,361,923,206 | 1,986 |
[
"WebAssembly",
"wabt"
] | ### Environment
```
OS : Linux ubuntu 5.15.0-46-generic #49~20.04.1-Ubuntu SMP Thu Aug 4 19:15:44 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
Commit : 3054d61f703d609995798f872fc86b462617c294
Version : 1.0.29
Build : make clang-debug-asan
```
### Proof of concept
poc_wasm2c-1.wasm
[poc_wasm2c-1.wasm.zip]... | Aborted in CWriter::Write at wasm2c | https://api.github.com/repos/WebAssembly/wabt/issues/1985/comments | 1 | 2022-09-05T12:58:25Z | 2022-10-03T06:27:37Z | https://github.com/WebAssembly/wabt/issues/1985 | 1,361,920,430 | 1,985 |
[
"WebAssembly",
"wabt"
] | ### Title
Aborted in CWriter::MangleType at wasm2c
### Environment
```
OS : Linux ubuntu 5.15.0-46-generic #49~20.04.1-Ubuntu SMP Thu Aug 4 19:15:44 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
Commit : 3054d61f703d609995798f872fc86b462617c294
Version : 1.0.29
Build : make clang-debug-asan
```
### Proof o... | Aborted in CWriter::MangleType at wasm2c | https://api.github.com/repos/WebAssembly/wabt/issues/1984/comments | 5 | 2022-09-05T12:57:12Z | 2023-03-17T16:55:00Z | https://github.com/WebAssembly/wabt/issues/1984 | 1,361,918,475 | 1,984 |
[
"WebAssembly",
"wabt"
] | ### Environment
```
OS : Linux ubuntu 5.15.0-46-generic #49~20.04.1-Ubuntu SMP Thu Aug 4 19:15:44 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
Commit : 3054d61f703d609995798f872fc86b462617c294
Version : 1.0.29
Build : make clang-debug-asan
```
### Proof of concept
poc-interp-3.wasm
[poc-interp-3.wasm.zip]... | Out-of-bound read in OnReturnCallIndirectExpr->GetReturnCallDropKeepCount | https://api.github.com/repos/WebAssembly/wabt/issues/1983/comments | 1 | 2022-09-05T12:51:24Z | 2022-09-17T19:15:54Z | https://github.com/WebAssembly/wabt/issues/1983 | 1,361,907,936 | 1,983 |
[
"WebAssembly",
"wabt"
] | ### Environment
```
OS : Linux ubuntu 5.15.0-46-generic #49~20.04.1-Ubuntu SMP Thu Aug 4 19:15:44 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
Commit : 3054d61f703d609995798f872fc86b462617c294
Version : 1.0.29
Build : make clang-debug-asan
```
### Proof of concept
poc-interp-2.wasm
[poc-interp-2.wasm.zip]... | Out-of-bound read in OnReturnCallExpr->GetReturnCallDropKeepCount | https://api.github.com/repos/WebAssembly/wabt/issues/1982/comments | 1 | 2022-09-05T12:50:49Z | 2022-09-17T19:13:47Z | https://github.com/WebAssembly/wabt/issues/1982 | 1,361,906,900 | 1,982 |
[
"WebAssembly",
"wabt"
] | ### Environment
```
OS : Linux ubuntu 5.15.0-46-generic #49~20.04.1-Ubuntu SMP Thu Aug 4 19:15:44 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
Commit : 3054d61f703d609995798f872fc86b462617c294
Version : 1.0.29
Build : make clang-debug-asan
```
### Proof of concept
poc-interp-1.wasm
[poc-interp-1.wasm.... | heap overflow in wasm-interp | https://api.github.com/repos/WebAssembly/wabt/issues/1981/comments | 1 | 2022-09-05T12:50:09Z | 2022-09-17T19:11:15Z | https://github.com/WebAssembly/wabt/issues/1981 | 1,361,905,751 | 1,981 |
[
"WebAssembly",
"wabt"
] | Even before my changes to the build (i.e. try on tag `1.0.29`) the code for running git-describe did nothing because of the following bogus check:
https://github.com/WebAssembly/wabt/blob/3054d61f703d609995798f872fc86b462617c294/CMakeLists.txt#L53-L55
On a tagged version like `1.0.29`, the `CMAKE_PROJECT_VERSION`... | The git describe code does nothing | https://api.github.com/repos/WebAssembly/wabt/issues/1978/comments | 0 | 2022-09-01T15:21:41Z | 2022-09-05T18:59:22Z | https://github.com/WebAssembly/wabt/issues/1978 | 1,359,025,257 | 1,978 |
[
"WebAssembly",
"wabt"
] | When configuring a git-clone of wabt on a non-tagged commit (like `main`), the following warning is issued:
```
CMake Warning at CMakeLists.txt:46 (message):
fatal: No names found, cannot describe anything.
Error running git describe to determine version
```
This comes from `git describe --tags` failing. | Noisy warnings from git describe | https://api.github.com/repos/WebAssembly/wabt/issues/1977/comments | 0 | 2022-09-01T14:46:21Z | 2022-09-05T18:59:22Z | https://github.com/WebAssembly/wabt/issues/1977 | 1,358,969,371 | 1,977 |
[
"WebAssembly",
"wabt"
] | Hi, this is the first time I'm posting here and also the first time I'm trying to install wabt, so please bare with me if this isn't the right place to place this question. With that said, here it is.
I am trying to install wabt on Kali Linux but cmake is giving me a strange error that I can't get past... It tells m... | No such file or directory wasm2c.top.h | https://api.github.com/repos/WebAssembly/wabt/issues/1975/comments | 1 | 2022-08-30T19:25:54Z | 2022-08-30T19:52:43Z | https://github.com/WebAssembly/wabt/issues/1975 | 1,356,204,121 | 1,975 |
[
"WebAssembly",
"wabt"
] | When running the full test suite on i386, many floating-point-related failures occur. The test summary is reproduced below.
```
**** FAILED ******************************************************************
- test/spec/float_exprs.txt
/ws/build/spectest-interp out/test/spec/float_exprs/float_exprs.json
- tes... | Many floating-point errors on i386 | https://api.github.com/repos/WebAssembly/wabt/issues/1973/comments | 2 | 2022-08-27T22:29:39Z | 2023-01-08T22:06:49Z | https://github.com/WebAssembly/wabt/issues/1973 | 1,353,189,285 | 1,973 |
[
"WebAssembly",
"wabt"
] | When running the unittests on an s390x Docker image, the Rot13 test fails.
```
[ RUN ] InterpTest.Rot13
../src/test-interp.cc:546: Failure
Expected equality of these values:
"Uryyb, JroNffrzoyl!"
string_data
Which is: "Hello, WebAssembly!"
[ FAILED ] InterpTest.Rot13 (8 ms)
```
Here is a li... | Rot13 test fails on s390x | https://api.github.com/repos/WebAssembly/wabt/issues/1972/comments | 10 | 2022-08-27T21:02:39Z | 2025-02-21T12:48:35Z | https://github.com/WebAssembly/wabt/issues/1972 | 1,353,144,015 | 1,972 |
[
"WebAssembly",
"wabt"
] | Hi, I'm using the `wast2json` tool to generate the test suites.
In the spec test suites [L190-L192](https://github.com/WebAssembly/spec/blob/main/test/core/memory_init.wast#L190-L192) and [L227-L229](https://github.com/WebAssembly/spec/blob/main/test/core/memory_init.wast#L227-L229), authought they are the `assert_inv... | Lost Data Count Section when encoding from WAT in `wast2json` tool | https://api.github.com/repos/WebAssembly/wabt/issues/1959/comments | 4 | 2022-08-14T01:02:29Z | 2022-09-01T14:28:40Z | https://github.com/WebAssembly/wabt/issues/1959 | 1,338,101,026 | 1,959 |
[
"WebAssembly",
"wabt"
] | Hi,
I found that when I encode the following WAT into WASM by the `wat2wasm` binary tool in both `1.0.29` or `master`:
(The WAT is in the [test case of the multiple memories proposal](https://github.com/WebAssembly/multi-memory/blob/main/test/core/memory-multi.wast#L47-L84))
```
(module
(memory 1)
(memory... | Wrong encoding WAT format with the multiple memories proposal | https://api.github.com/repos/WebAssembly/wabt/issues/1958/comments | 4 | 2022-08-14T00:09:41Z | 2022-08-15T21:39:35Z | https://github.com/WebAssembly/wabt/issues/1958 | 1,338,088,244 | 1,958 |
[
"WebAssembly",
"wabt"
] | 0000004: error: bad magic value | decompiling error | https://api.github.com/repos/WebAssembly/wabt/issues/1956/comments | 2 | 2022-08-11T23:17:00Z | 2024-06-26T02:48:27Z | https://github.com/WebAssembly/wabt/issues/1956 | 1,336,584,807 | 1,956 |
[
"WebAssembly",
"wabt"
] | The `wasm2wat` works fine, but `wasm2c` returns:
`000002c: error: invalid section code: 12`
Full output:
wasm2wat:
```
(module
(import "env" "__linear_memory" (memory (;0;) 1))
(data $_ZN5woff210kKnownTagsE (i32.const 0) "pamcdaehaehhxtmhpxameman2/SOtsop tvcmgpffylgacolperp FFCGROVTDBECLBEpsagxmdhnrekHSTLTLC... | 000002c: error: invalid section code: 12 | https://api.github.com/repos/WebAssembly/wabt/issues/1955/comments | 3 | 2022-08-11T14:44:31Z | 2022-08-14T23:53:18Z | https://github.com/WebAssembly/wabt/issues/1955 | 1,336,067,579 | 1,955 |
[
"WebAssembly",
"wabt"
] | Hi,
Here I am back again with some stupid question.
The module I'm trying to run dynamically allocates with `malloc` (It's an emscripten WASM binary)
I've worked out sending pointers from the inner runtime to the outside by "transforming" the pointer to `&memory->data[pointer]`, so my runtime can read the value... | [wasm2c] Passing pointer from outside of the runtime to inside the runtime | https://api.github.com/repos/WebAssembly/wabt/issues/1953/comments | 1 | 2022-07-26T11:37:37Z | 2022-07-26T13:56:10Z | https://github.com/WebAssembly/wabt/issues/1953 | 1,318,112,888 | 1,953 |
[
"WebAssembly",
"wabt"
] | If I make a roundtrip through wabt of an object file, then some objects from WriteBinaryModule() end up with:
```
emnm libskia.SkGeometry.o
/opt/emscripten-llvm/bin/llvm-nm: error: ./libskia.SkGeometry.o: duplicate symbol name sqrtf
```
I'm not really sure whats special about the sqrtf symbol in this object, b... | Roundtrip of object through ReadBinaryIR() -> WriteBinaryModule() result in : emnm : Error duplicate symbol. | https://api.github.com/repos/WebAssembly/wabt/issues/1952/comments | 10 | 2022-07-21T19:34:01Z | 2022-09-18T05:55:37Z | https://github.com/WebAssembly/wabt/issues/1952 | 1,313,711,717 | 1,952 |
[
"WebAssembly",
"wabt"
] | I've been debugging my transformation, and I've found if I read in a wasm file with ReadBinaryIR() and then just write it back with no modification using WriteBinaryModule(), then I can't link with the new object. E.g. emnm gives and error, out of order section type:0
Interestingly, if I then do:
```
wasm2wat ou... | wabbt - ReadBinaryIR() -> WriteBinaryModule() -> emnm output.o :: error: output.o: out of order section type: 0 | https://api.github.com/repos/WebAssembly/wabt/issues/1951/comments | 1 | 2022-07-21T14:12:56Z | 2022-07-21T15:40:39Z | https://github.com/WebAssembly/wabt/issues/1951 | 1,313,328,605 | 1,951 |
[
"WebAssembly",
"wabt"
] | Hi,
Lately I've been reverse engineering some software on the web that uses WebAssembly. I'm pretty familiar with it as I have developed applications with it myself. I found this beautiful program `wasm2c` to aid me in my efforts, but now I'm looking to inject code into the binary. My idea was to use `wasm2c` to dec... | (wasm2c) Re-compiling to WASM | https://api.github.com/repos/WebAssembly/wabt/issues/1950/comments | 8 | 2022-07-20T15:45:53Z | 2023-03-07T11:47:33Z | https://github.com/WebAssembly/wabt/issues/1950 | 1,311,382,556 | 1,950 |
[
"WebAssembly",
"wabt"
] | wasm-rt.h is not fully documented on the following points, which is an issue when evaluating wasm2c for embedded targets (or any project that cannot rely on wasm-rt-impl.c):
* What headers generated code and wasm-rt.h are depending on ? E.g. currently wasm-rt.h depends on `#include <setjmp.h>`. While standard, embed... | wasm2c's wasm-rt.h documentation | https://api.github.com/repos/WebAssembly/wabt/issues/1949/comments | 5 | 2022-07-20T11:32:56Z | 2022-08-15T17:50:15Z | https://github.com/WebAssembly/wabt/issues/1949 | 1,310,901,617 | 1,949 |
[
"WebAssembly",
"wabt"
] | Hi,
I would like to add a tool to wabt, that can make some simple modifications to the wasm module loaded.
I've tried to iterate through the module and make some some changes, like renaming the functions..
But when I write the binary again, nothing has changed.
Is it possible to do something like this with wa... | How to implement a transformation. | https://api.github.com/repos/WebAssembly/wabt/issues/1948/comments | 1 | 2022-07-18T22:53:02Z | 2022-07-19T00:04:57Z | https://github.com/WebAssembly/wabt/issues/1948 | 1,308,772,170 | 1,948 |
[
"WebAssembly",
"wabt"
] | I was playing with tables and it _seems_ that `wat2wasm` doesnβt support `elem` sections as they are defined [spec](https://webassembly.github.io/spec/core/text/modules.html#element-segments). However, I might also be reading the spec wrong.
Here are some examples I _think_ should work, but donβt:
```wat
;; `ite... | Element sections not fully spec compliant? | https://api.github.com/repos/WebAssembly/wabt/issues/1946/comments | 4 | 2022-07-17T22:27:58Z | 2022-07-18T14:38:57Z | https://github.com/WebAssembly/wabt/issues/1946 | 1,307,225,822 | 1,946 |
[
"WebAssembly",
"wabt"
] | I have a WASM program written in text format that uses the `table.size` instruction.
When using wat2wasm, and then passing that output to wasm2c, I get the following error:
error: unexpected opcode: 0xfc 0x10
I'm using WABT 1.0.29 on macOS.
FYI, I also use `table.grow`. | wasm2c: Support `table.size` | https://api.github.com/repos/WebAssembly/wabt/issues/1944/comments | 2 | 2022-07-10T17:46:29Z | 2022-07-13T18:44:40Z | https://github.com/WebAssembly/wabt/issues/1944 | 1,299,977,908 | 1,944 |
[
"WebAssembly",
"wabt"
] | Hello!
Just getting started with WebAssembly. Downloaded, built, and installed the `wabt` repository on my Windows system.
I created a simple `.wat` file (`test.wat`):
```wat
(module)
```
Then, I ran `wat2wasm` to "parse and typecheck" the file:
```bash
$ wat2wasm test.wat
```
I was surprised to see t... | wat2wasm compiles to .wasm with no options, contrary to documentation | https://api.github.com/repos/WebAssembly/wabt/issues/1941/comments | 4 | 2022-07-07T02:56:18Z | 2022-07-08T20:40:33Z | https://github.com/WebAssembly/wabt/issues/1941 | 1,296,723,883 | 1,941 |
[
"WebAssembly",
"wabt"
] | ### Environment
```
OS : Linux ubuntu 5.13.0-51-generic #58~20.04.1-Ubuntu SMP Tue Jun 14 11:29:12 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
Commit : 57e6a58bfdd0babfd6f7fe401c9f2d8238ec3213
Version : 1.0.29
```
### Proof of concept
[poc.wasm.zip](https://github.com/WebAssembly/wabt/files/8973781/poc.wasm.... | Segmentation fault in wabt::cat_compute_size | https://api.github.com/repos/WebAssembly/wabt/issues/1938/comments | 1 | 2022-06-24T06:43:25Z | 2023-03-17T11:32:55Z | https://github.com/WebAssembly/wabt/issues/1938 | 1,283,331,255 | 1,938 |
[
"WebAssembly",
"wabt"
] | The goal is to run the code locally with wasmtime.
wat from WasmFiddle
[native_messaging_host_c_wat.txt](https://github.com/WebAssembly/wabt/files/8945714/native_messaging_host_c_wat.txt)
Errors from wat2wasm demo
```
β
Error: parseWat failed:
test.wast:11:11: error: unexpected token "anyfunc", expec... | wat2wasm demo throws error for wat from wasdk/WasmFiddle | https://api.github.com/repos/WebAssembly/wabt/issues/1937/comments | 6 | 2022-06-21T04:15:35Z | 2022-06-21T07:56:02Z | https://github.com/WebAssembly/wabt/issues/1937 | 1,277,857,168 | 1,937 |
[
"WebAssembly",
"wabt"
] | ```
PS C:\users\XXXXXX\desktop\wabt-main\build> cmake .. -DCMAKE_BUILD_TYPE=DEBUG -DCMAKE_INSTALL_PREFIX=..\ -G "Visual Studio 17 2022"
-- Selecting Windows SDK version 10.0.19041.0 to target Windows 10.0.19044.
-- The C compiler identification is MSVC 19.30.30709.0
-- The CXX compiler identification is MSVC 19.30.... | Trying to CMake on windows but got Configuring incomplete | https://api.github.com/repos/WebAssembly/wabt/issues/1936/comments | 1 | 2022-06-15T03:26:35Z | 2022-06-17T14:40:03Z | https://github.com/WebAssembly/wabt/issues/1936 | 1,271,618,242 | 1,936 |
[
"WebAssembly",
"wabt"
] | wasm2c (v1.0.23) throws 0000075: error: invalid section code: 12
Checked spec, and there is such a section:
https://webassembly.github.io/spec/core/binary/modules.html#data-count-section | 0000075: error: invalid section code: 12 | https://api.github.com/repos/WebAssembly/wabt/issues/1935/comments | 1 | 2022-06-14T22:02:50Z | 2022-06-15T05:05:52Z | https://github.com/WebAssembly/wabt/issues/1935 | 1,271,410,993 | 1,935 |
[
"WebAssembly",
"wabt"
] | I have a WASM program written in text format that uses bulk memory operations.
When using wat2wasm, and then passing that output to wasm2c, I get the following error:
> error: unexpected opcode: 0xfc 0xa
I'm using WABT 1.0.29 on macOS. | Bulk memory problem with wat2wasm + wasm2c | https://api.github.com/repos/WebAssembly/wabt/issues/1934/comments | 2 | 2022-06-10T18:44:35Z | 2022-07-13T18:45:33Z | https://github.com/WebAssembly/wabt/issues/1934 | 1,267,891,964 | 1,934 |
[
"WebAssembly",
"wabt"
] | from the example https://github.com/WebAssembly/wabt/blob/main/wasm2c/README.md, no multi instance example.
I mean create multi vm instance, and load diff module and run at diff memory block. | multi instance of wasm2c support | https://api.github.com/repos/WebAssembly/wabt/issues/1933/comments | 6 | 2022-06-02T09:34:23Z | 2022-06-21T05:50:51Z | https://github.com/WebAssembly/wabt/issues/1933 | 1,257,938,064 | 1,933 |
[
"WebAssembly",
"wabt"
] | Commit: `83a226bcd1816c86fb1fcb0963c6a11e2c373aaf`
## Reproduce
Sample: [interp_sig_index_oob.zip](https://github.com/WebAssembly/wabt/files/8789638/interp_sig_index_oob.zip)
```bash
./wasm-objdump -d interp_sig_index_oob.wasm
./wasm-interp --enable-tail-call interp_sig_index_oob.wasm
```
Output:
``... | Out-of-bound Read at `BinaryReaderInterp::OnReturnCallIndirectExpr` | https://api.github.com/repos/WebAssembly/wabt/issues/1929/comments | 2 | 2022-05-27T20:45:58Z | 2022-09-17T18:35:32Z | https://github.com/WebAssembly/wabt/issues/1929 | 1,251,258,400 | 1,929 |
[
"WebAssembly",
"wabt"
] | Tried with d8517aa9.
test.wast:
```wast
(module binary
"\00asm" "\01\00\00\00"
"\04\04\01" ;; Table section with 1 entry
"\70\00\00" ;; no max, minimum 0, funcref
"\09\09\01" ;; Element section with 1 entry
"\02" ... | wast2json changes element section contents in `(module binary ...)` | https://api.github.com/repos/WebAssembly/wabt/issues/1927/comments | 13 | 2022-05-26T13:46:57Z | 2022-06-06T18:04:31Z | https://github.com/WebAssembly/wabt/issues/1927 | 1,249,597,202 | 1,927 |
[
"WebAssembly",
"wabt"
] | I convert the file into a C file and compile the code using gcc.
`mv webgl.wasm.unity webgl.wasm.gz`
`gunzip webgl.wasm.gz`
`wasm2c webgl.wasm`
`gcc -c webgl.wasm -o webgl`
gcc quits the shell without any prompt. | Use wasm2c to convert unityweb into c | https://api.github.com/repos/WebAssembly/wabt/issues/1926/comments | 1 | 2022-05-25T05:51:30Z | 2022-05-25T07:35:39Z | https://github.com/WebAssembly/wabt/issues/1926 | 1,247,521,729 | 1,926 |
[
"WebAssembly",
"wabt"
] | wasm2c is failing several spec tests if we add `-O` or `-O2` to the compiler command line.
- Example commit here: https://github.com/fixpointOS/wabt/commit/551b3dba69f9d35ddf0271e0e0383e3525d2e50f
- Corresponding CI output on Ubuntu: https://github.com/fixpointOS/wabt/runs/6547538885?check_suite_focus=true
There... | Several spec tests fail if wasm2c output compiled with `-O` or `-O2` | https://api.github.com/repos/WebAssembly/wabt/issues/1925/comments | 5 | 2022-05-23T21:59:01Z | 2022-07-12T00:12:50Z | https://github.com/WebAssembly/wabt/issues/1925 | 1,245,740,051 | 1,925 |
[
"WebAssembly",
"wabt"
] | Commit: `d8517aa922ddd3ffd6d7f28f00d2bb0f9853cf88`
## Reproduce
Fuzzed Sample: [wabt_decomp_is_name_assert.zip](https://github.com/WebAssembly/wabt/files/8750089/wabt_decomp_is_name_assert.zip)
Simplified Sample:
```
$ cat simplified.wat
(module
(type (;0;) (func (result i64)))
(func (;0;) (type 0)... | Assertion `is_name()` failed at wasm-decompiler caused by empty global name | https://api.github.com/repos/WebAssembly/wabt/issues/1924/comments | 3 | 2022-05-22T19:08:09Z | 2022-09-17T18:35:32Z | https://github.com/WebAssembly/wabt/issues/1924 | 1,244,340,785 | 1,924 |
[
"WebAssembly",
"wabt"
] | Commit: `d8517aa922ddd3ffd6d7f28f00d2bb0f9853cf88`
## Reproduce
Fuzzed Sample: [decomp_heap_of.zip](https://github.com/WebAssembly/wabt/files/8748689/decomp_heap_of.zip)
Simplified Sample:
```
$ cat simplified.wat
(module
(type (;0;) (func (param i32 i64 i64 f32) (result i32 i64 i64 f64)))
(func (... | Memory corruption at wasm-decompile caused by unmatched parameters | https://api.github.com/repos/WebAssembly/wabt/issues/1923/comments | 1 | 2022-05-22T03:14:08Z | 2022-05-22T03:54:00Z | https://github.com/WebAssembly/wabt/issues/1923 | 1,244,134,438 | 1,923 |
[
"WebAssembly",
"wabt"
] | Commit: `d8517aa922ddd3ffd6d7f28f00d2bb0f9853cf88`
## Reproduce
Fuzzed Sample:
[decomp_size_ge_nargs.zip](https://github.com/WebAssembly/wabt/files/8748269/decomp_size_ge_nargs.zip)
Simplified Sample:
```bash
$ cat simplified.wat
(module
(type (;0;) (func (param i32 i32) (result i32)))
(func (;0;)... | OOB Read at wasm-decompile caused by lack of BrTable handling | https://api.github.com/repos/WebAssembly/wabt/issues/1922/comments | 0 | 2022-05-21T19:52:13Z | 2022-09-17T18:35:31Z | https://github.com/WebAssembly/wabt/issues/1922 | 1,244,068,730 | 1,922 |
[
"WebAssembly",
"wabt"
] | null | any way to link multi wat file to one module? | https://api.github.com/repos/WebAssembly/wabt/issues/1921/comments | 1 | 2022-05-17T09:26:10Z | 2022-05-17T20:44:30Z | https://github.com/WebAssembly/wabt/issues/1921 | 1,238,347,331 | 1,921 |
[
"WebAssembly",
"wabt"
] | Commit: `d8517aa922ddd3ffd6d7f28f00d2bb0f9853cf88`
Reproduce:
```bash
./wasm2wat_fuzzer < ./wabt_intrusive_list_back.wasm
```
Stack Trace:
```
#4 0x00000000004c3963 in wabt::intrusive_list<wabt::Expr>::back() ()
#5 0x00000000004c2cfa in wabt::(anonymous namespace)::BinaryReaderIR::TopLabelExpr(wabt::(an... | Assertion `!empty()` failed at `wabt::intrusive_list<wabt::Expr>::back()` of `intrusive-list.h:402` | https://api.github.com/repos/WebAssembly/wabt/issues/1920/comments | 0 | 2022-05-16T17:33:19Z | 2022-05-18T01:38:09Z | https://github.com/WebAssembly/wabt/issues/1920 | 1,237,478,158 | 1,920 |
[
"WebAssembly",
"wabt"
] | It looks like `wamrc` currently supports generating LLVM optimized and unoptimzed code. I am looking to run some instrumentation passes on this LL file and generate an AoT executable again.
However, function labels seem to be discarded in the generated LL file (particularly the `main` or `start` function), and it c... | wamrc: Compiling generated LL files | https://api.github.com/repos/WebAssembly/wabt/issues/1916/comments | 2 | 2022-05-03T19:43:28Z | 2022-05-03T22:56:06Z | https://github.com/WebAssembly/wabt/issues/1916 | 1,224,535,960 | 1,916 |
[
"WebAssembly",
"wabt"
] | In the process of re-compiling the output of `wasm2c`, the `wasm-rt-impl.c` file requires `setjmp.h`, which cannot be found by the wasi-sdk clang release.
How do you get around this? Thanks! | wasm2c compilation error: 'setjmp.h' cannot be found | https://api.github.com/repos/WebAssembly/wabt/issues/1914/comments | 8 | 2022-05-03T14:56:25Z | 2022-05-18T01:49:13Z | https://github.com/WebAssembly/wabt/issues/1914 | 1,224,214,725 | 1,914 |
[
"WebAssembly",
"wabt"
] | null | F | https://api.github.com/repos/WebAssembly/wabt/issues/1913/comments | 0 | 2022-05-02T01:28:30Z | 2022-05-02T03:15:15Z | https://github.com/WebAssembly/wabt/issues/1913 | 1,222,378,738 | 1,913 |
[
"WebAssembly",
"wabt"
] | (Spinning this off from https://github.com/WebAssembly/wabt/pull/1814#discussion_r850917266)
Here is a proposal for how to improve safety when linking multiple modules together with wasm2c.
As background:
- At present, for every import **or** export, wasm2c writes an extern declaration in the generated header ... | wasm2c linking safety (enforcing import subtyping rules at compile time) | https://api.github.com/repos/WebAssembly/wabt/issues/1908/comments | 9 | 2022-04-26T09:03:12Z | 2022-07-04T06:24:27Z | https://github.com/WebAssembly/wabt/issues/1908 | 1,215,636,966 | 1,908 |
[
"WebAssembly",
"wabt"
] | Tried https://webassembly.github.io/wabt/demo/wat2wasm/ feeding in some simple Wat with exception definitions:
I do not get the errors if I run the tool manually. | Make online wat2wasm respect the enable exception flag | https://api.github.com/repos/WebAssembly/wabt/issues/1906/comments | 8 | 2022-04-25T06:32:44Z | 2022-12-23T04:53:16Z | https://github.com/WebAssembly/wabt/issues/1906 | 1,214,037,831 | 1,906 |
[
"WebAssembly",
"wabt"
] | Since this is a repo in the org for the W3C core recommendation, I think it is a fair ask to have a flag that constrains features to what's included in that, and no more. It will help with tracking https://github.com/WebAssembly/wabt#supported-proposals and make upgrades seamless.
I'm not asking for this to be by de... | Add a flag that constrains features to the W3C recommendation | https://api.github.com/repos/WebAssembly/wabt/issues/1899/comments | 7 | 2022-04-14T00:02:48Z | 2022-04-14T00:36:09Z | https://github.com/WebAssembly/wabt/issues/1899 | 1,203,896,313 | 1,899 |
[
"WebAssembly",
"wabt"
] | When function indices are used in `ref.func`, there is a check to make sure the index is declared in the element section before the code section.
However, this check is too strong in wabt as uses in the global section should be ok. Example:
```
;; the reference in the global is ok
(module (func $f1) (global fun... | [reference types]: `ref.func` declaration check is overly strict | https://api.github.com/repos/WebAssembly/wabt/issues/1893/comments | 1 | 2022-04-12T20:43:59Z | 2022-04-13T20:07:30Z | https://github.com/WebAssembly/wabt/issues/1893 | 1,202,368,716 | 1,893 |
[
"WebAssembly",
"wabt"
] | It would be great to be able to copy-paste the binary .wasm output as base64 rather than having to download it.
Thank you! | RFE: Make online wat2wasm demo output base64 | https://api.github.com/repos/WebAssembly/wabt/issues/1891/comments | 4 | 2022-04-07T16:20:24Z | 2022-04-26T18:15:59Z | https://github.com/WebAssembly/wabt/issues/1891 | 1,196,285,223 | 1,891 |
[
"WebAssembly",
"wabt"
] | An example program like the following should fail during validation:
```
;;; TOOL: wat2wasm
;;; ARGS: --enable-function-references
;;; ERROR: 1
(module
(func (param $f (ref $x)) (result f32))
)
(;; STDERR ;;;
;;; STDERR ;;)
```
Because the `ref $x` is unbound.
Right now this will trigger an assert... | Typed funcref: handle unbound type names in validation | https://api.github.com/repos/WebAssembly/wabt/issues/1890/comments | 2 | 2022-04-05T02:05:16Z | 2022-04-11T09:35:16Z | https://github.com/WebAssembly/wabt/issues/1890 | 1,192,511,737 | 1,890 |
[
"WebAssembly",
"wabt"
] | When building wabt-1.0.28 with gcc-12.0.1 (Fedora 36 Beta), I'm getting these new testsuite failures:
```
...
- test/wasm2c/spec/names.txt
expected error code 0, got 1.
STDERR MISMATCH:
--- expected
+++ actual
@@ -0,0 +1,139 @@
+In file included from out/test/wasm2c/spec/names/names.2.c:5:
+out/... | testsuite failures due to new warnings in GCC 12 | https://api.github.com/repos/WebAssembly/wabt/issues/1885/comments | 1 | 2022-04-04T08:13:52Z | 2023-03-15T02:06:03Z | https://github.com/WebAssembly/wabt/issues/1885 | 1,191,419,770 | 1,885 |
[
"WebAssembly",
"wabt"
] | This is the wat file used:
```wat
(module
(func $how_old (param $year_now i32) (param $year_born i32) (result i32)
get_local $year_now
get_local $year_born
i32.sub)
(export "how_old" (func $how_old))
)
```
I am using the binary for 1.0.28 | wat2wasm failing with: unexpected token get_local, expected ). | https://api.github.com/repos/WebAssembly/wabt/issues/1883/comments | 3 | 2022-04-02T17:03:22Z | 2022-04-03T04:20:40Z | https://github.com/WebAssembly/wabt/issues/1883 | 1,190,685,597 | 1,883 |
[
"WebAssembly",
"wabt"
] | Non-null references are opcode `-0x15` and are supported already in wabt. Nullable references (opcode `-0x14`) should also be supported.
https://github.com/WebAssembly/function-references/blob/main/proposals/function-references/Overview.md#binary-format | Typed funcref support should include nullable references | https://api.github.com/repos/WebAssembly/wabt/issues/1882/comments | 0 | 2022-04-01T18:46:37Z | 2022-04-01T18:46:46Z | https://github.com/WebAssembly/wabt/issues/1882 | 1,190,154,931 | 1,882 |
[
"WebAssembly",
"wabt"
] | A test like the following currently crashes in type-checking:
```
;;; TOOL: wat2wasm
;;; ARGS: --enable-function-references
;;; ERROR: 1
(module
(type $f32-f32-1 (func (param f32) (result f32)))
(type $f32-f32-2 (func (param f32) (result f32)))
(func $foo (param $f (ref $f32-f32-1)) (result f32)
... | Type funcref crash due to ref type getting read as "any" type instead of a ref type | https://api.github.com/repos/WebAssembly/wabt/issues/1881/comments | 1 | 2022-04-01T17:15:47Z | 2022-04-04T23:36:38Z | https://github.com/WebAssembly/wabt/issues/1881 | 1,190,074,424 | 1,881 |
[
"WebAssembly",
"wabt"
] | On line 311, undefined is spelled as undefine.
@nickvidal can I work on this? | Omitted letter in word in the README.md file | https://api.github.com/repos/WebAssembly/wabt/issues/1879/comments | 0 | 2022-04-01T12:18:54Z | 2022-04-04T16:49:18Z | https://github.com/WebAssembly/wabt/issues/1879 | 1,189,715,160 | 1,879 |
[
"WebAssembly",
"wabt"
] | 1.24 has no problem, but current versions including latest mistake the table element ID for re-defining the element:
```bash
~/Downloads/wabt-1.0.28/bin/wast2json --debug-names ./tests/spectest/testdata/elem.wast
./tests/spectest/testdata/elem.wast:16:4: error: redefinition of elem "$t"
(elem $t (i32.const 0)... | Issue decoding table elements | https://api.github.com/repos/WebAssembly/wabt/issues/1878/comments | 7 | 2022-04-01T06:22:31Z | 2022-04-14T00:11:12Z | https://github.com/WebAssembly/wabt/issues/1878 | 1,189,302,941 | 1,878 |
[
"WebAssembly",
"wabt"
] | There is some support for the GC proposal in wabt already behind a flag, but it predates the current design for the proposal (that recently went to phase 2) that includes new type constructs like `rec`, `sub`, and so on.
Now that the design is more stable, it could be a good time to catch up support in wabt. I'm int... | Update GC proposal support to recent phase 2 version | https://api.github.com/repos/WebAssembly/wabt/issues/1874/comments | 3 | 2022-03-30T17:11:08Z | 2023-12-14T17:04:38Z | https://github.com/WebAssembly/wabt/issues/1874 | 1,186,754,270 | 1,874 |
[
"WebAssembly",
"wabt"
] | null | add an homebrew method of installation for all tools | https://api.github.com/repos/WebAssembly/wabt/issues/1873/comments | 8 | 2022-03-28T14:07:37Z | 2022-03-29T15:18:20Z | https://github.com/WebAssembly/wabt/issues/1873 | 1,183,498,549 | 1,873 |
[
"WebAssembly",
"wabt"
] | Attempting to use wat2wasm.exe on Twitch's source, downloadable [here](https://static.twitchcdn.net/assets/amazon-ivs-wasmworker.min-516e603bd6ff6160ceb3.wasm), produces this error:
`wat2wasm.exe amazon-ivs-wasmworker.min-516e603bd6ff6160ceb3.wasm -o out.wasm`
```
amazon-ivs-wasmworker.min-516e603bd6ff6160ceb3.wasm:... | wat2wasm error: unexpected token current_memory | https://api.github.com/repos/WebAssembly/wabt/issues/1868/comments | 3 | 2022-03-17T12:56:19Z | 2022-03-22T21:08:25Z | https://github.com/WebAssembly/wabt/issues/1868 | 1,172,349,579 | 1,868 |
[
"WebAssembly",
"wabt"
] | @sbc100
I have updated the test suite according to your suggestion.
There are 94 new failures introduced. Output:
https://gist.github.com/zherczeg/be736057cf92b09c1d6eed752f548c4b
The following files are added (count: 81). It seems all of them fails, although I have not checked all of them. Maybe these needs t... | Update test suite | https://api.github.com/repos/WebAssembly/wabt/issues/1867/comments | 1 | 2022-03-17T09:21:24Z | 2022-04-01T18:11:38Z | https://github.com/WebAssembly/wabt/issues/1867 | 1,172,124,620 | 1,867 |
[
"WebAssembly",
"wabt"
] | I'm not quite sure if this a bug, but I think it's not quite in sync with the official spec.
From my wasm file's disassembly, wasm-objdump generate the following line:
```
00b994: 11 87 80 80 80 00 00 | call_indirect 7 0
```
This here should have the type index 7 and the table index 0. Unfortunately... | call_indirect in wasm-objdump switches x and y | https://api.github.com/repos/WebAssembly/wabt/issues/1865/comments | 7 | 2022-03-12T21:53:15Z | 2022-03-17T17:56:15Z | https://github.com/WebAssembly/wabt/issues/1865 | 1,167,410,684 | 1,865 |
[
"WebAssembly",
"wabt"
] | This is probably not within the purvey of `WebAssembly` though you are th experts re compilation/decompilation of native code, and Google recommends migrating from Native Client to WebAssembly https://developer.chrome.com/docs/native-client/migration/.
Google released an extension which relies on Native Client that ... | How to extract source code from Native Client .nexe file, migrate to WebAssembly? | https://api.github.com/repos/WebAssembly/wabt/issues/1864/comments | 8 | 2022-03-12T16:29:31Z | 2022-03-14T01:20:35Z | https://github.com/WebAssembly/wabt/issues/1864 | 1,167,333,582 | 1,864 |
[
"WebAssembly",
"wabt"
] | My wat is :
```
(module
(func $thirteen (result i32) (i32.const 13))
(func $fourtytwo (result i32) (i32.const 42))
(table (export "tbl") anyfunc (elem $thirteen $fourtytwo))
)
```
when i excute οΌ
`wat2wasm table.wat -o table.wasm`
I get an error:
```
table.wat:4:25: error: unexpected token "... | unexpected token "anyfunc", expected a natural number | https://api.github.com/repos/WebAssembly/wabt/issues/1863/comments | 3 | 2022-03-11T10:05:31Z | 2022-03-30T19:17:26Z | https://github.com/WebAssembly/wabt/issues/1863 | 1,166,228,497 | 1,863 |
[
"WebAssembly",
"wabt"
] | ;tldr; I think we should.
It has been proposed in #1833 that we don't need to be mangling the names at all (except to turn them into valid C symbols).
In particular there is no need to append the mangled signature to the symbol names. e.g. foo_vi (for a void function `foo` that takes an i32).
For exports ther... | Should we remove signature mangling from wasm2c output? | https://api.github.com/repos/WebAssembly/wabt/issues/1858/comments | 8 | 2022-03-09T19:25:18Z | 2022-04-14T07:58:11Z | https://github.com/WebAssembly/wabt/issues/1858 | 1,164,345,903 | 1,858 |
[
"WebAssembly",
"wabt"
] | Currently it seems these are the only tests that test `--disable-`:
- https://github.com/WebAssembly/wabt/blob/1f3a1d5fae0296fdf503968131905be9e8f40cf4/test/parse/expr/atomic-disabled.txt
- https://github.com/WebAssembly/wabt/blob/1f3a1d5fae0296fdf503968131905be9e8f40cf4/test/parse/expr/bulk-memory-disabled.txt
- ... | There should be more tests for --enable- and --disable- | https://api.github.com/repos/WebAssembly/wabt/issues/1837/comments | 1 | 2022-02-22T16:05:12Z | 2022-02-22T16:07:20Z | https://github.com/WebAssembly/wabt/issues/1837 | 1,147,093,907 | 1,837 |
[
"WebAssembly",
"wabt"
] | Running the 1.0.25 testsuite on 32-bit ARM and 32-bit x86 yields failures in these tests:
```
dump/reference-types.txt
dump/relocations-all-features.txt
dump/relocations.txt
dump/table.txt
```
I can reproduce this across all currently supported Fedora releases (34, 35 and rawhide).
Log extract below:
```
[...... | 1.0.25: new test failures on 32-bit arches | https://api.github.com/repos/WebAssembly/wabt/issues/1822/comments | 4 | 2022-02-08T09:24:59Z | 2022-04-04T08:32:03Z | https://github.com/WebAssembly/wabt/issues/1822 | 1,126,994,136 | 1,822 |
[
"WebAssembly",
"wabt"
] | Build from source on macOS 12.3 beta with cmake 3.19.2
The input file (add1.wat) should not contain any errors.
```
(module
(func $add (param $lhs i32) (param $rhs i32) (result i32)
get_local $lhs
get_local $rhs
i32.add)
(export "add" (func $add))
)
```
Run `wat2wasm add1.wat -o add.wasm... | wabt2wasm error: unexpected token get_local | https://api.github.com/repos/WebAssembly/wabt/issues/1820/comments | 2 | 2022-02-04T05:58:54Z | 2022-02-04T09:12:19Z | https://github.com/WebAssembly/wabt/issues/1820 | 1,123,846,818 | 1,820 |
[
"WebAssembly",
"wabt"
] | I was inspecting the binary wasm file to clarify the wasm spec, and I noticed that version `1.0.23` of `wat2wasm` was producing non-canonical varints, for the `i32.const` I checked on the current main branch and it's a problem there too, it doesn't seem it was fixed by: https://github.com/WebAssembly/wabt/pull/1632
... | wat2wasm produces non-cannonical varint | https://api.github.com/repos/WebAssembly/wabt/issues/1816/comments | 2 | 2022-01-31T13:13:22Z | 2023-02-13T08:47:26Z | https://github.com/WebAssembly/wabt/issues/1816 | 1,119,412,881 | 1,816 |
[
"WebAssembly",
"wabt"
] | So far as I can tell, wasm-objdump doesn't use local names when printing instructions such as local.get. I wanted to check if this was so (rather than, for instance, my test file specifying the names incorrectly -- wasm2wat includes the names, so I assume this isn't the case), and whether there would be any interest in... | Local names in wasm-objdump -x | https://api.github.com/repos/WebAssembly/wabt/issues/1815/comments | 1 | 2022-01-30T21:58:44Z | 2022-02-02T20:27:44Z | https://github.com/WebAssembly/wabt/issues/1815 | 1,118,732,646 | 1,815 |
[
"WebAssembly",
"wabt"
] | According to [the MVP spec](https://www.w3.org/TR/wasm-core-1/#text-functype), a type can include symbolic IDs for parameters. It [elaborates](https://www.w3.org/TR/wasm-core-1/#functions%E2%91%A2) that a function's local index is its parameters followed by its locals. Finally, it [states](https://www.w3.org/TR/wasm-co... | text format: local index isn't enforced on type parameter IDs | https://api.github.com/repos/WebAssembly/wabt/issues/1813/comments | 1 | 2022-01-25T01:31:55Z | 2022-01-26T23:25:10Z | https://github.com/WebAssembly/wabt/issues/1813 | 1,113,321,744 | 1,813 |
[
"WebAssembly",
"wabt"
] | Why is WABT version 1.0.26 marked as a pre-release version and not the latest version?
My unit test use https://github.com/WebAssembly/wabt/releases/latest for execution and are broken. | 1.0.26 Pre-release | https://api.github.com/repos/WebAssembly/wabt/issues/1812/comments | 0 | 2022-01-22T13:48:08Z | 2022-02-19T11:38:39Z | https://github.com/WebAssembly/wabt/issues/1812 | 1,111,569,221 | 1,812 |
[
"WebAssembly",
"wabt"
] | Some features are really hard to implement without typed unions like std::variant and other features from c++17.
For example, with typed function references and gc proposal we have named types during parsing `(ref null $foo_func)` and `(ref null $struct_type)` but we can't just add `std::string` to struct Type becau... | Move to c++ 17 | https://api.github.com/repos/WebAssembly/wabt/issues/1811/comments | 1 | 2022-01-21T12:33:40Z | 2022-02-11T17:41:49Z | https://github.com/WebAssembly/wabt/issues/1811 | 1,110,421,726 | 1,811 |
[
"WebAssembly",
"wabt"
] | Latest version 1.0.25 seems to fail reading param names following a type field. this is allowed by spec and works with wasm-tools. https://www.w3.org/TR/wasm-core-1/#type-uses%E2%91%A0
```
(module
(type $i32i32_i32 (func (param i32 i32) (result i32)))
(import "Math" "Mul" (func $mul (param $x f32)... | Fails reading local name after inlined type | https://api.github.com/repos/WebAssembly/wabt/issues/1806/comments | 3 | 2022-01-13T23:47:22Z | 2022-01-15T00:17:42Z | https://github.com/WebAssembly/wabt/issues/1806 | 1,102,595,529 | 1,806 |
[
"WebAssembly",
"wabt"
] | Hello all,
I would like to start a conversation about the best way to make wasm2c thread-safe so that the same module can be instantiated multiple times with different memory contexts, and functions from different instances can be executed in parallel. Our current plan was to move global memory variables into a stru... | Thoughts on making wasm2c thread-safe | https://api.github.com/repos/WebAssembly/wabt/issues/1805/comments | 4 | 2022-01-13T21:11:55Z | 2022-04-14T23:28:59Z | https://github.com/WebAssembly/wabt/issues/1805 | 1,102,382,737 | 1,805 |
[
"WebAssembly",
"wabt"
] | running `wasm-strip` 1.0.24 on one of our Rust-compiled, with SIMD enabled, WASM modules fails with:
```
0000a70: error: expected valid local type
```
and another similar one (repro binary: [opcode_fail_module.wasm.zip](https://github.com/WebAssembly/wabt/files/7854907/opcode_fail_module.wasm.zip)) fail with:
``... | wasm-strip fails on module with SIMD instructions | https://api.github.com/repos/WebAssembly/wabt/issues/1803/comments | 2 | 2022-01-12T13:28:07Z | 2022-04-27T04:41:45Z | https://github.com/WebAssembly/wabt/issues/1803 | 1,100,343,043 | 1,803 |
[
"WebAssembly",
"wabt"
] | I have downloaded **wabt** in my Linux Mint machine, but when I try to use the **wat2wasm _file.wat_** command into a simple example like this, it gives me error.
```
(module
(func $add (param $lhs i32) (param $rhs i32) (result i32)
get_local $lhs
get_local $rhs
i32.add)
(export "add" (func $add))
)
```
T... | wat2wasm gives error: unexpected token get_local | https://api.github.com/repos/WebAssembly/wabt/issues/1802/comments | 6 | 2022-01-11T20:13:17Z | 2022-09-05T07:52:55Z | https://github.com/WebAssembly/wabt/issues/1802 | 1,099,576,889 | 1,802 |
[
"WebAssembly",
"wabt"
] | See https://github.com/WebAssembly/binaryen/issues/4418 for details. It looks like on imported functions wabt's name section emitting code will emit an empty name for params. That is, the empty string "". That seems like a bug to me as it is not useful for a debugger (the index would be better than the name). | Empty param name in name section for imported functions | https://api.github.com/repos/WebAssembly/wabt/issues/1799/comments | 9 | 2022-01-06T21:23:34Z | 2022-01-08T21:48:39Z | https://github.com/WebAssembly/wabt/issues/1799 | 1,095,706,985 | 1,799 |
[
"WebAssembly",
"wabt"
] | In `SharedValidator::OnFuncType`, there is this code:
```
if (!options_.features.multi_value_enabled() && result_count > 1) {
result |=
PrintError(loc, "multiple result values not currently supported.");
}
```
WABT does indeed support multi-value, however.
Maybe the error message should say 'n... | Wording of error message 'multiple result values not currently supported' | https://api.github.com/repos/WebAssembly/wabt/issues/1796/comments | 2 | 2021-12-23T19:47:54Z | 2022-01-10T15:59:46Z | https://github.com/WebAssembly/wabt/issues/1796 | 1,087,956,833 | 1,796 |
[
"WebAssembly",
"wabt"
] | Describe the bug
A bug was found within the wabt. Though it might not be an intended use of the relevant API, the bug can still produce critical issues within a program using wabt. It would be best if the affected logic is checked beforehand.
The bug was found with a fuzzer based on the function "WastParser.LongToken... | Bug report on wabt( AddressSanitizer: OOM) | https://api.github.com/repos/WebAssembly/wabt/issues/1794/comments | 0 | 2021-12-23T01:25:28Z | 2022-09-18T05:13:37Z | https://github.com/WebAssembly/wabt/issues/1794 | 1,087,297,335 | 1,794 |
[
"WebAssembly",
"wabt"
] | Describe the bug
A bug was found within the wabt. Though it might not be an intended use of the relevant API, the bug can still produce critical issues within a program using wabt. It would be best if the affected logic is checked beforehand.
The bug was found with a fuzzer based on the function "string_view.rfind2".... | Bug report on wabt( AddressSanitizer: SEGV) | https://api.github.com/repos/WebAssembly/wabt/issues/1793/comments | 2 | 2021-12-23T01:22:31Z | 2022-09-18T05:13:56Z | https://github.com/WebAssembly/wabt/issues/1793 | 1,087,296,349 | 1,793 |
[
"WebAssembly",
"wabt"
] | Compile the following program with `clang-13 -target wasm32-wasi -O0`. Use `wasm-objdump -s -d -x -r --section-offsets expr.o` to disassemble it, it fails with `Data reloctions outside of segments`.
```c
int bar(int);
void* sha = bar;
int foo(int x) {
void *p = bar;
sha = p;
if (x < 0) {
return ... | "Data reloctions outside of segments" | https://api.github.com/repos/WebAssembly/wabt/issues/1790/comments | 0 | 2021-12-17T13:34:29Z | 2022-01-07T22:23:16Z | https://github.com/WebAssembly/wabt/issues/1790 | 1,083,267,072 | 1,790 |
[
"WebAssembly",
"wabt"
] | /root/wasm/wabt/src/interp/interp-wasm-c-api.cc: In constructor βwasm_globaltype_t::wasm_globaltype_t(wasm_valtype_t*, wasm_mutability_t)β:
/root/wasm/wabt/src/interp/interp-wasm-c-api.cc:129:22: error: could not convert β* typeβ from βwasm_valtype_tβ to βwabt::interp::ValueType {aka wabt::Type}β
valtype{*ty... | Build failed on CentOS 7 | https://api.github.com/repos/WebAssembly/wabt/issues/1773/comments | 2 | 2021-12-05T10:29:01Z | 2022-04-27T04:45:49Z | https://github.com/WebAssembly/wabt/issues/1773 | 1,071,423,894 | 1,773 |
[
"WebAssembly",
"wabt"
] | If my wasm includes `"βΊ\n"` or `"\e2\98\ba\n"`, it behaves normally. I would expect `"\u{263a}\n"` to end up with the same byte sequence, but it fails compilation like:
```bash
$ smiley.wat
smiley.wat:6:39: error: bad escape "\u"
(data (global.get $start_string) "\u{263a}\n")
... | wat2wasm doesn't seem to accept utf escapes | https://api.github.com/repos/WebAssembly/wabt/issues/1767/comments | 3 | 2021-11-30T06:26:41Z | 2022-05-03T08:34:39Z | https://github.com/WebAssembly/wabt/issues/1767 | 1,066,845,715 | 1,767 |
[
"WebAssembly",
"wabt"
] | Hi there,
I was trying to convert a WASM to C when wasm2c exited saying that the WASM file used threads.
Would it be possible to enable this feature in wasm2c?
Thanks | wasm2c supporting threads and other features | https://api.github.com/repos/WebAssembly/wabt/issues/1766/comments | 14 | 2021-11-21T18:45:04Z | 2021-12-07T21:02:09Z | https://github.com/WebAssembly/wabt/issues/1766 | 1,059,454,802 | 1,766 |
[
"WebAssembly",
"wabt"
] | When running the example in #1761 with tracing on, you get a crash due to an assertion failure like the following
```
$ wabt/out/clang/Debug/wasm-interp out/test/interp/return-call-get-local/return-call-get-local.wasm -t --run-all-exports --enable-tail-call
>>> running export "f":
#0. 0: V:0 | i64.const 1
#0... | Assertion fails in `return_call` test case when tracing is on | https://api.github.com/repos/WebAssembly/wabt/issues/1763/comments | 0 | 2021-11-17T00:54:18Z | 2021-11-17T00:54:18Z | https://github.com/WebAssembly/wabt/issues/1763 | 1,055,589,649 | 1,763 |
[
"WebAssembly",
"wabt"
] | The following test case will cause an infinite loop (despite there being no recursion in these calls):
```
;;; TOOL: run-interp
;;; ARGS*: --enable-tail-call
(module
(func (export "f") (result i32)
(i64.const 1)
(return_call $g))
(func $g (param i64) (result i32)
(i32.const 3)
(return_... | Infinite loop on use of `return_call` | https://api.github.com/repos/WebAssembly/wabt/issues/1761/comments | 1 | 2021-11-16T19:09:11Z | 2022-01-07T20:22:16Z | https://github.com/WebAssembly/wabt/issues/1761 | 1,055,226,626 | 1,761 |
[
"WebAssembly",
"wabt"
] | If we have binaries attached for common architectures, less need to burn CPU compiling from source. Linux and MacOS are common now, and Windows will be common soon enough. How about attaching bins at least for Linux and MacOS for arm64? | Add release binaries for arm64 | https://api.github.com/repos/WebAssembly/wabt/issues/1760/comments | 2 | 2021-11-15T06:25:37Z | 2022-02-07T22:39:20Z | https://github.com/WebAssembly/wabt/issues/1760 | 1,053,264,651 | 1,760 |
[
"WebAssembly",
"wabt"
] | May I ask the supporting plan about the latest [GC MVP](https://github.com/WebAssembly/gc/blob/master/proposals/gc/MVP.md)? The [GC branch](https://github.com/WebAssembly/wabt/tree/gc) hasn't been updated for a long time. | GC supporting | https://api.github.com/repos/WebAssembly/wabt/issues/1759/comments | 1 | 2021-11-11T01:50:58Z | 2022-03-13T22:54:06Z | https://github.com/WebAssembly/wabt/issues/1759 | 1,050,489,887 | 1,759 |
[
"WebAssembly",
"wabt"
] | Currently trying to run wasm-strip on Wasm using e.g. multithreading results in errors like
```
0001115: error: memory may not be shared: threads not allowed
```
and/or
```
0005364: error: invalid section code: 12
```
There is no reason for wasm-strip to care about those parts of the Wasm binary; instea... | wasm-strip should not error out on post-MVP extensions | https://api.github.com/repos/WebAssembly/wabt/issues/1757/comments | 1 | 2021-11-08T16:58:25Z | 2021-11-09T00:08:06Z | https://github.com/WebAssembly/wabt/issues/1757 | 1,047,685,997 | 1,757 |
[
"WebAssembly",
"wabt"
] | https://github.com/WebAssembly/spec/blob/e87021b46a7519ff5264e62fa4773e4c92ded57a/test/core/elem.wast#L470-L484
```log
$ wast2json --enable-all --no-check -o elem.json elem.wast
elem.wast:473:55: error: unexpected token (, expected ).
(elem (i32.const 0) funcref (item (ref.null func) (ref.null func)))
... | wast2json fails to convert elem.wast from ther core spec | https://api.github.com/repos/WebAssembly/wabt/issues/1750/comments | 1 | 2021-11-04T10:08:25Z | 2022-04-27T04:36:02Z | https://github.com/WebAssembly/wabt/issues/1750 | 1,044,555,698 | 1,750 |
[
"WebAssembly",
"wabt"
] | I'm seeing: `Segment/Elem offset must be an i32 init expr ` when I tree to `wasm-objdump -h hello.o` after building with `emcc -c -s MEMORY64=2`.
Looks like we unconditionally expect 32-bit offsets, which I guess is not correct?
https://github.com/WebAssembly/wabt/blob/cd6639980cebed23d07bce4973284cf980f70721/s... | wasm-objdump error's on object files built with wasm64 | https://api.github.com/repos/WebAssembly/wabt/issues/1742/comments | 2 | 2021-10-18T19:59:41Z | 2021-10-25T21:15:56Z | https://github.com/WebAssembly/wabt/issues/1742 | 1,029,536,979 | 1,742 |
[
"WebAssembly",
"wabt"
] | Many test fail because the recent spec tests now require multi-table and reference-type support. I was forced to delete the following tests for that reason:
- test/wasm2c/spec/br_table.txt
- test/wasm2c/spec/call_indirect.txt
- test/wasm2c/spec/elem.txt
- test/wasm2c/spec/exports.txt
- test/wasm2c/spec/impor... | wasm2c no longer passes many spec tests | https://api.github.com/repos/WebAssembly/wabt/issues/1737/comments | 0 | 2021-10-15T01:28:00Z | 2022-10-03T06:27:37Z | https://github.com/WebAssembly/wabt/issues/1737 | 1,026,982,267 | 1,737 |
[
"WebAssembly",
"wabt"
] | I use [wasm2wat demo](https://webassembly.github.io/wabt/demo/wasm2wat/) with all features enabled:
<img width="542" alt="ζͺε±2021-10-15 08 20 07" src="https://user-images.githubusercontent.com/10240841/137412779-112a4799-95dc-4c02-8268-63ed77b32a82.png">
The .wasm file is attatched:
[a.out.wasm.zip](https:/... | unexpected opcode: 0x18 | https://api.github.com/repos/WebAssembly/wabt/issues/1736/comments | 2 | 2021-10-15T00:28:39Z | 2022-08-17T05:17:21Z | https://github.com/WebAssembly/wabt/issues/1736 | 1,026,942,362 | 1,736 |
[
"WebAssembly",
"wabt"
] | Current top-of-tree (and also v1.0.24) emit warnings when built with most recent CMake versions:
```
CMake Warning (dev) at CMakeLists.txt:352 (add_library):
Policy CMP0115 is not set: Source file extensions must be explicit. Run
"cmake --help-policy CMP0115" for policy details. Use the cmake_policy
comm... | CMake warnings when building with CMake v3.20+ | https://api.github.com/repos/WebAssembly/wabt/issues/1720/comments | 1 | 2021-10-04T17:48:02Z | 2022-05-19T18:00:52Z | https://github.com/WebAssembly/wabt/issues/1720 | 1,015,456,249 | 1,720 |
[
"WebAssembly",
"wabt"
] | I've been using the latest WebAssembly spec to implement my library, [wasup](https://github.com/nicholaslyang/wasup). Since the Bulk Memory proposal is marked as finished, the current spec includes the DataCount section. Therefore, I was a little confused when I started getting `invalid section code: 12` errors with my... | Bulk Memory As Default | https://api.github.com/repos/WebAssembly/wabt/issues/1717/comments | 0 | 2021-09-28T04:27:07Z | 2021-10-13T16:33:32Z | https://github.com/WebAssembly/wabt/issues/1717 | 1,009,189,643 | 1,717 |
[
"WebAssembly",
"wabt"
] | In the Windows instructions in the README.md, it suggests using MinGw and links to mingw.org but that URL currently seems to be serving malware. | mingw.org leads to malware site | https://api.github.com/repos/WebAssembly/wabt/issues/1716/comments | 2 | 2021-09-27T21:47:44Z | 2022-08-17T20:19:32Z | https://github.com/WebAssembly/wabt/issues/1716 | 1,008,661,703 | 1,716 |
[
"WebAssembly",
"wabt"
] | I am a bit confused about the opcode.def file - what do the parameters represent?
These are the control instructions from the official specification:
Note that both the `br` and the `br_if` instructi... | opcode.def Structure | https://api.github.com/repos/WebAssembly/wabt/issues/1715/comments | 3 | 2021-09-23T14:25:53Z | 2021-09-29T14:21:30Z | https://github.com/WebAssembly/wabt/issues/1715 | 1,005,501,699 | 1,715 |
[
"WebAssembly",
"wabt"
] | For instance, `ZN4hvif5shape5Shape5parse17ha264877da5eed17bE()` should be something like `hvif::shape::Shape::parse()`.
This issue is related to #1406, but specific to the symbols generated by rustc. | Demangle Rust symbol names in wasm-decompile | https://api.github.com/repos/WebAssembly/wabt/issues/1711/comments | 1 | 2021-09-16T19:41:19Z | 2023-08-15T02:47:40Z | https://github.com/WebAssembly/wabt/issues/1711 | 998,568,097 | 1,711 |
[
"WebAssembly",
"wabt"
] | It appears that WABT uses https://github.com/WebAssembly/testsuite for it's spec tests. However it has outdated versions for some of the proposals, i.e exception-handling. When I try to take a fresh version directly from the https://github.com/WebAssembly/exception-handling I see a multitude of different issues in the ... | Spec tests for the exception handling don't work | https://api.github.com/repos/WebAssembly/wabt/issues/1710/comments | 3 | 2021-09-16T13:02:57Z | 2022-04-27T04:54:49Z | https://github.com/WebAssembly/wabt/issues/1710 | 998,188,423 | 1,710 |
[
"WebAssembly",
"wabt"
] | When compiling on an arm64 Mac, configuring the build produces the warning:
```
CMake Warning at CMakeLists.txt:197 (message):
Unknown target architecture!
```
This is a common enough architecture now that it should be handled without warning. | TARGET_ARCH sniffing doesn't handle arm64 on OSX | https://api.github.com/repos/WebAssembly/wabt/issues/1709/comments | 2 | 2021-09-15T20:42:03Z | 2022-09-28T22:43:22Z | https://github.com/WebAssembly/wabt/issues/1709 | 997,500,719 | 1,709 |
[
"WebAssembly",
"wabt"
] | On RHEL/CentOS 7, the system python3 is 3.6. Before python 3.7.0 (see [3.7.0 alpha 1 changelog](https://docs.python.org/3.7/whatsnew/changelog.html#id186), [issue 28180](https://bugs.python.org/issue28180) and [PEP 538](https://www.python.org/dev/peps/pep-0538)), the default text encoding was ascii, which fails on Unic... | 1.0.24: test/wasm2c/spec/names.txt fails on RHEL/CentOS 7 with system python-3.6 | https://api.github.com/repos/WebAssembly/wabt/issues/1704/comments | 1 | 2021-08-20T12:46:05Z | 2022-04-04T08:03:43Z | https://github.com/WebAssembly/wabt/issues/1704 | 975,578,222 | 1,704 |
Subsets and Splits
Unique Owner-Repo Count
Counts the number of unique owner-repos in the dataset, providing a basic understanding of diverse repositories.