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"
] | wabt 1.0.24 fails to compile with system compiler (gcc-4.8.5) on RHEL/CentOS 7:
```
[ 83%] Building CXX object CMakeFiles/wasm.dir/src/interp/interp-wasm-c-api.cc.o
/usr/bin/c++ -DWASM_API_EXTERN="__attribute__((visibility(\"default\")))" -D__STDC_FORMAT_MACROS=1 -D__STDC_LIMIT_MACROS=1 -Dwasm_EXPORTS -I/builddir/b... | 1.0.24 compilation error with gcc-4.8.5 (RHEL/CentOS 7) | https://api.github.com/repos/WebAssembly/wabt/issues/1703/comments | 1 | 2021-08-20T12:16:51Z | 2021-08-20T13:42:43Z | https://github.com/WebAssembly/wabt/issues/1703 | 975,557,329 | 1,703 |
[
"WebAssembly",
"wabt"
] | I don't mean to sound ungrateful, but it has to be said... The issue tracker is just piling up, and simple questions often get ignored for years and forgotten. | Is WABT actively maintained? | https://api.github.com/repos/WebAssembly/wabt/issues/1694/comments | 4 | 2021-08-01T01:49:55Z | 2022-04-27T18:52:34Z | https://github.com/WebAssembly/wabt/issues/1694 | 957,360,669 | 1,694 |
[
"WebAssembly",
"wabt"
] | ## update: jump to the bottom of all this ...
Pipes are used to give the output (stdout) of a command as the input (stdin) to another command ... command line piping has always been a power part of the Unix command line. This feature is absent in wabt. Is this something to consider ... as the concept is already bein... | accommodate outputting the binary wasm to stdout | https://api.github.com/repos/WebAssembly/wabt/issues/1692/comments | 3 | 2021-07-13T01:07:45Z | 2022-04-27T05:00:18Z | https://github.com/WebAssembly/wabt/issues/1692 | 942,583,259 | 1,692 |
[
"WebAssembly",
"wabt"
] | I'm using the `readWasm` method of WABTJS, and it's choking on any constant expression that contains more than one instruction. The [Extended Constant Expressions Proposal][1] adds `add`, `sub` and `mul` instructions (so long as they are integer-typed) to the instructions permitted in a constant expression, so support ... | WABT cannot handle constant expressions with more than one instruction. | https://api.github.com/repos/WebAssembly/wabt/issues/1690/comments | 1 | 2021-07-11T02:22:48Z | 2022-04-27T05:03:02Z | https://github.com/WebAssembly/wabt/issues/1690 | 941,357,801 | 1,690 |
[
"WebAssembly",
"wabt"
] | The first sample works with 1.0.23 but produce with the version `main` from today an error.
error: `test.wat:2:10: error: undefined function variable "$.<start>"`
command line: `wat2wasm.exe test.wat --enable-all`
OS: Windows 10
```
(module
(start $.<start>)
(event (param externref))
(func $.<start>
... | wat2wasm: function variable resolution broken | https://api.github.com/repos/WebAssembly/wabt/issues/1689/comments | 6 | 2021-07-10T15:53:39Z | 2021-08-29T13:54:00Z | https://github.com/WebAssembly/wabt/issues/1689 | 941,276,428 | 1,689 |
[
"WebAssembly",
"wabt"
] | I'm trying to build wabt on an apple M1 computer running Big Sur 11.3.1 and I get this error message:
CMake Warning at CMakeLists.txt:197 (message):
Unknown target architecture! | wabt does not build on Apple M1 computers | https://api.github.com/repos/WebAssembly/wabt/issues/1688/comments | 1 | 2021-07-07T13:13:02Z | 2022-09-28T22:43:22Z | https://github.com/WebAssembly/wabt/issues/1688 | 938,880,364 | 1,688 |
[
"WebAssembly",
"wabt"
] | When converting a binary that contains an extended name section to WAT, the identifiers are all preserved, except type and label identifiers, which are seemingly just ignored. | Type identifiers in the name section are lost during round trip. | https://api.github.com/repos/WebAssembly/wabt/issues/1687/comments | 2 | 2021-07-06T01:31:54Z | 2022-09-18T22:17:56Z | https://github.com/WebAssembly/wabt/issues/1687 | 937,445,289 | 1,687 |
[
"WebAssembly",
"wabt"
] | Over in https://github.com/bytecodealliance/wasm-tools/issues/281 we were wondering why we were seeing validation errors for what should be valid Wasm:
```
(module
(memory 1)
(func
i32.const 0
v128.const i32x4 0 0 0 0
v128.load32_lane align=1 0
drop
)
)
```
The following co... | error: alignment (0) must be a power of 2 | https://api.github.com/repos/WebAssembly/wabt/issues/1674/comments | 0 | 2021-06-09T17:33:55Z | 2021-08-06T16:53:04Z | https://github.com/WebAssembly/wabt/issues/1674 | 916,448,831 | 1,674 |
[
"WebAssembly",
"wabt"
] | Tried out building on windows, using the instructions in README.md, and received compilation failures.
1. mkdir artifacts
2. cd artifacts
3. cmake ..
4. cmake --build . --config DEBUG --target install
Did I miss a step?
Result:
```
Build FAILED.
"C:\repos\oss\wabt\artifacts\install.vcxproj" (default... | Cannot open include file: 'wasm.h': No such file or directory | https://api.github.com/repos/WebAssembly/wabt/issues/1673/comments | 1 | 2021-06-04T01:22:13Z | 2021-06-04T01:24:39Z | https://github.com/WebAssembly/wabt/issues/1673 | 910,985,264 | 1,673 |
[
"WebAssembly",
"wabt"
] | Hi all,
I'm trying to run the wasm-interp as WebAssembly runtime in my project.
I found a memory issue which is that the heap memory allocated through wasm-interp increases steadily without any drop.
Let me give you an example about function call,
https://github.com/WebAssembly/wabt/blob/63c350984f7dbe76f5963f4df... | memory management(gc) in wasm-interp | https://api.github.com/repos/WebAssembly/wabt/issues/1671/comments | 1 | 2021-05-26T10:09:20Z | 2022-02-09T06:40:44Z | https://github.com/WebAssembly/wabt/issues/1671 | 902,143,179 | 1,671 |
[
"WebAssembly",
"wabt"
] | I'm getting new test failures with 1.0.23 on s390x running Fedora 34. The failing tests are:
```
- test/spec/simd/simd_load16_lane.txt
- test/spec/simd/simd_load32_lane.txt
- test/spec/simd/simd_load64_lane.txt
- test/spec/simd/simd_load8_lane.txt
- test/spec/simd/simd_store16_lane.txt
- test/spec/simd/simd_stor... | test failures on s390x | https://api.github.com/repos/WebAssembly/wabt/issues/1670/comments | 5 | 2021-05-14T13:17:24Z | 2021-08-09T17:55:50Z | https://github.com/WebAssembly/wabt/issues/1670 | 891,915,510 | 1,670 |
[
"WebAssembly",
"wabt"
] | `wasm2c` uses `_t` *everywhere*, which is reserved by POSIX and should not be used. It'd be nice to fix this at some point, altho it is a breaking change. | POSIX reserved names: *_t is reserved by POSIX | https://api.github.com/repos/WebAssembly/wabt/issues/1668/comments | 0 | 2021-05-06T10:59:24Z | 2021-05-06T10:59:24Z | https://github.com/WebAssembly/wabt/issues/1668 | 877,373,537 | 1,668 |
[
"WebAssembly",
"wabt"
] | ### enviroment
- windows with release 1.0.23
- placed the Dynlib.dll and the wasm2c file with same directory
- kali is the same
### command && report
`.\wasm2c.exe easywasm.wasm -o ret.c
0000018: error: unable to read u32 leb128: needed_dynlibs` | unable to read u32 leb128 | https://api.github.com/repos/WebAssembly/wabt/issues/1667/comments | 3 | 2021-05-01T12:42:15Z | 2023-02-13T10:14:17Z | https://github.com/WebAssembly/wabt/issues/1667 | 873,662,885 | 1,667 |
[
"WebAssembly",
"wabt"
] | Check the attached example. For some reason `wasm-decompile` produces multiple identical declarations for the same variables:
```
var b:{ a:int, b:int, c:int, d:int, e:int, f:int, g:int, h:int, i:int, j:int, k:int, l:int }
var d:int;
var d:int;
var c:{ a:int, b:int, c:int, d:int, e:int, f:int, g:int, h:i... | [wasm-decompile] Same variable declaration gets emitted multiple times | https://api.github.com/repos/WebAssembly/wabt/issues/1665/comments | 3 | 2021-04-23T11:17:01Z | 2021-04-26T23:14:25Z | https://github.com/WebAssembly/wabt/issues/1665 | 866,013,812 | 1,665 |
[
"WebAssembly",
"wabt"
] | When compiling the text format, it would be useful to have a flag that causes any passive segments to be indexed ahead of any active segments, but otherwise in their lexical order.
Unfortunately, bulk-memory operations have already been standardized, and this feature would be a breaking change if applied everywhere,... | [wat2wasm] Add a flag for indexing passive segments before active segments. | https://api.github.com/repos/WebAssembly/wabt/issues/1663/comments | 3 | 2021-04-18T17:10:27Z | 2021-06-04T02:10:03Z | https://github.com/WebAssembly/wabt/issues/1663 | 860,713,943 | 1,663 |
[
"WebAssembly",
"wabt"
] | Is there any documentation on how to read the wasm-interp trace output? I can intuitively understand some of it, but most of the output is ambigous to me. For instance I was debugging an issue:
```
>>> running export "bench":
#0. 0: V:0 | alloca 4
#0. 8: V:4 | global.get $0
#0. 16: V:5 | i32.const 32
... | Document wasm-interp trace output | https://api.github.com/repos/WebAssembly/wabt/issues/1662/comments | 0 | 2021-04-11T15:26:58Z | 2021-04-11T15:28:22Z | https://github.com/WebAssembly/wabt/issues/1662 | 855,334,648 | 1,662 |
[
"WebAssembly",
"wabt"
] | I'm writing a compiler that targets Wasm by generating .wat files, and then compiling those using wat2wasm. However, there are some parts of the runtime that I'd like to write using another language, such as C (or Rust), rather than having to hand-craft .wat files. It seems as though a potential route is to compile the... | Guide for creating object files using wat2wasm | https://api.github.com/repos/WebAssembly/wabt/issues/1658/comments | 13 | 2021-04-06T08:18:54Z | 2021-04-20T20:56:09Z | https://github.com/WebAssembly/wabt/issues/1658 | 851,163,683 | 1,658 |
[
"WebAssembly",
"wabt"
] | This may be another LLVM problem; if so, sorry for the noise. However, if nothing else I think the error message could probably be improved.
Using emscripten tot:
```
$ cat i64x2_eq.c
typedef __INT64_TYPE__ i64x2 __attribute__((__vector_size__(16)));
i64x2 eq(i64x2 a, i64x2 b) {
return __builtin_wasm_eq_... | [SIMD] wasm2wat "error: type mismatch in function, expected [] but got [v128]" from i64x2.eq | https://api.github.com/repos/WebAssembly/wabt/issues/1655/comments | 4 | 2021-03-29T14:23:32Z | 2021-08-05T23:32:44Z | https://github.com/WebAssembly/wabt/issues/1655 | 843,423,230 | 1,655 |
[
"WebAssembly",
"wabt"
] | With emscripten tot and this code:
```c
typedef char i8x16 __attribute__((__vector_size__(16)));
i8x16 popcnt(i8x16 v) {
return __builtin_wasm_popcnt_i8x16(v);
}
```
wasm2wat thinks the popcnt instruction is an `i16x8.extadd_pairwise`
```
$ emcc -O3 -msimd128 -c -o popcnt.wasm popcnt.c && wasm2wat --... | [SIMD] wasm2wat outputs incorrect instruction for i8x16.popcount | https://api.github.com/repos/WebAssembly/wabt/issues/1653/comments | 7 | 2021-03-24T15:43:06Z | 2021-03-30T15:28:30Z | https://github.com/WebAssembly/wabt/issues/1653 | 839,860,509 | 1,653 |
[
"WebAssembly",
"wabt"
] | ### Test Case
```wat
;; test.wat
(module
(table (;0;) 102 102 funcref)
(elem (;0;) (i32.const 1) func))
```
### Steps to Reproduce
```shell
$ wat2wasm test.wat -o test.wasm
$ wasm2wat --generate-names test.wasm -o with-names.wat
$ wat2wasm with-names.wat -o with-names.wasm
with-names.wat:3:4: erro... | `wasm2wat --generate-names` produces invalid names | https://api.github.com/repos/WebAssembly/wabt/issues/1651/comments | 5 | 2021-03-23T23:29:30Z | 2023-03-01T00:30:44Z | https://github.com/WebAssembly/wabt/issues/1651 | 839,204,399 | 1,651 |
[
"WebAssembly",
"wabt"
] | I suspect this is a known issue, but recording it here:
emcc will allow you to compile with `-pthread`, and generate nice wrapper callers for POSIX pthread calls. I'd expect that invoking with `--wasi --enable-threads` would allow wasm code of this form to load and run, but it fails at load time with `wasi error: un... | wasm-interp --wasi --enable-threads can't handle emcc's pthread support | https://api.github.com/repos/WebAssembly/wabt/issues/1645/comments | 5 | 2021-03-17T17:37:23Z | 2021-03-17T20:40:46Z | https://github.com/WebAssembly/wabt/issues/1645 | 834,026,568 | 1,645 |
[
"WebAssembly",
"wabt"
] | Uploaded a test case:
[wasm-objdump-fails.txt](https://github.com/WebAssembly/wabt/files/6110933/wasm-objdump-fails.txt)
```
$ wasm-objdump -d wasm-objdump-fails.txt
clusterfuzz-testcase-minimized-v8_wasm_async_fuzzer-5664681130524672: file format wasm 0x1
Code Disassembly:
00002d func[0] <main>:
... | wasm-objdump cannot handle prefixed instructions with non-canonical leb128 opcodes | https://api.github.com/repos/WebAssembly/wabt/issues/1631/comments | 2 | 2021-03-09T19:32:52Z | 2023-02-13T10:16:47Z | https://github.com/WebAssembly/wabt/issues/1631 | 826,519,038 | 1,631 |
[
"WebAssembly",
"wabt"
] | Various compilation errors prevent compilation on 32-bit targets (e.g., x86-32). Sure would be handy to be able to build and use this tool on those systems. | Compilation is broken for 32-bit targets for WITH_WASI=ON | https://api.github.com/repos/WebAssembly/wabt/issues/1629/comments | 13 | 2021-03-06T00:40:56Z | 2021-03-11T18:59:56Z | https://github.com/WebAssembly/wabt/issues/1629 | 823,514,373 | 1,629 |
[
"WebAssembly",
"wabt"
] | At recent top-of-tree, building with `-DWITH_WASI=ON` fails, with many errors of the form
```
_deps/wabt-src/src/interp/interp-wasi.cc:255:35: error: 'i32_' is a private member of 'wabt::interp::Value'
```
Is WITH_WASI (still) supported? | WITH_WASI=ON is broken | https://api.github.com/repos/WebAssembly/wabt/issues/1627/comments | 0 | 2021-03-05T22:38:34Z | 2021-03-06T00:39:11Z | https://github.com/WebAssembly/wabt/issues/1627 | 823,469,354 | 1,627 |
[
"WebAssembly",
"wabt"
] | See [this spec test](https://github.com/WebAssembly/spec/pull/1293), it passes reference interpreter and it fails on WABT 1.0.21:
```
../imports.wast:574: error instantiating module: "actual size (1) smaller than declared (2)"
../imports.wast:579: unknown module in register
../imports.wast:580: unknown invoke "$M... | Incorrect min limit of exported memory after grow | https://api.github.com/repos/WebAssembly/wabt/issues/1626/comments | 1 | 2021-03-05T10:41:10Z | 2022-09-18T05:54:11Z | https://github.com/WebAssembly/wabt/issues/1626 | 822,965,063 | 1,626 |
[
"WebAssembly",
"wabt"
] | Seeing the following error when compiling macOS. It appears the `MAP_ANONYMOUS` flag may not be defined, but perhaps [`MAP_ANON`]( https://developer.apple.com/library/archive/documentation/System/Conceptual/ManPages_iPhoneOS/man2/mmap.2.html ) would be a good substitute
```
../wasm2c/wasm-rt-impl.c:133:58: error: u... | MAP_ANONYMOUS undefined on OS X 10.10 and earlier (pre-2015) | https://api.github.com/repos/WebAssembly/wabt/issues/1620/comments | 9 | 2021-03-03T07:16:10Z | 2023-02-13T10:16:18Z | https://github.com/WebAssembly/wabt/issues/1620 | 820,826,223 | 1,620 |
[
"WebAssembly",
"wabt"
] | In trying to build wabt 1.0.21 ran into the following compilation error:
```
../src/interp/interp-wasm-c-api.cc:17:10: fatal error: wasm.h: No such file or directory
17 | #include <wasm.h>
| ^~~~~~~~
compilation terminated.
```
More details can be found in PR ( https://github.com/conda-forg... | Missing wasm.h? | https://api.github.com/repos/WebAssembly/wabt/issues/1619/comments | 3 | 2021-03-02T21:37:18Z | 2021-03-03T15:41:11Z | https://github.com/WebAssembly/wabt/issues/1619 | 820,411,401 | 1,619 |
[
"WebAssembly",
"wabt"
] | Is there work underway to bring the WABT interpreter in line with the final proposal for the wasm-simd128 spec? If so, is there any rough ETA? If not, is this work scheduled to be done? (Or has it already been done and I somehow missed it?)
Halide currently uses the WABT interpreter for a fair number of our correctn... | Support for final wasm-simd128 specin the wabt interpreter? | https://api.github.com/repos/WebAssembly/wabt/issues/1617/comments | 9 | 2021-03-01T18:27:55Z | 2022-09-18T05:23:32Z | https://github.com/WebAssembly/wabt/issues/1617 | 819,134,114 | 1,617 |
[
"WebAssembly",
"wabt"
] | given the input
```c
int square(int a) {
if(a < 5) return 42;
return a*a;
} ... | [Q] clang/gas style assembly | https://api.github.com/repos/WebAssembly/wabt/issues/1616/comments | 3 | 2021-02-28T20:29:35Z | 2021-03-01T23:35:00Z | https://github.com/WebAssembly/wabt/issues/1616 | 818,302,092 | 1,616 |
[
"WebAssembly",
"wabt"
] | Seems like github offers a relatively easy way to do this these days. | Switch primary branch from `master` to `main` | https://api.github.com/repos/WebAssembly/wabt/issues/1613/comments | 3 | 2021-02-26T16:30:59Z | 2021-03-22T16:58:42Z | https://github.com/WebAssembly/wabt/issues/1613 | 817,495,568 | 1,613 |
[
"WebAssembly",
"wabt"
] | This snippet is invalid,
```wat
(module
(import "" "" (func $f))
(table 1 1 externref)
(elem (i32.const 0) $f)
)
```
as `func` is not a super-type of `externref`.
wat2wasm currently doesn't catch it. | wat2wasm doesn't typecheck (elem) against table types | https://api.github.com/repos/WebAssembly/wabt/issues/1612/comments | 1 | 2021-02-25T21:20:30Z | 2022-11-13T18:14:37Z | https://github.com/WebAssembly/wabt/issues/1612 | 816,819,291 | 1,612 |
[
"WebAssembly",
"wabt"
] | My very basic example at https://github.com/mvolkmann/wasm-demo gives the following error when I run it in Chrome, but the code still works as expected.
```text
inject.js:2 Uncaught SyntaxError: Invalid regular expression: /(?:[›][[()#;?]*(?:[0-9]{1,4}(?:;[0-9]{0,4})*)?[0-9A-PRZcf-nqry=><])|[ - -›Â​
︀-... | wat2wasm produces code that gives "Invalid regular expression" | https://api.github.com/repos/WebAssembly/wabt/issues/1611/comments | 3 | 2021-02-19T12:49:41Z | 2021-02-25T00:22:38Z | https://github.com/WebAssembly/wabt/issues/1611 | 811,997,083 | 1,611 |
[
"WebAssembly",
"wabt"
] | catch_all.wat:
```wasm
(module
(type (;0;) (func))
(func (;0;) (type 0)
try
catch_all
end))
```
If I create a wasm file using wat2wasm and disassemble it using wasm-objdump,
```
$ wat2wasm --enable-all catch_all.wat -o catch_all.wasm
$ wasm-objdump -d catch_all.wasm
```
The result is
... | wat2wasm still encodes 'catch_all' as 'else' | https://api.github.com/repos/WebAssembly/wabt/issues/1610/comments | 1 | 2021-02-18T21:49:50Z | 2021-02-19T15:15:52Z | https://github.com/WebAssembly/wabt/issues/1610 | 811,495,737 | 1,610 |
[
"WebAssembly",
"wabt"
] | Reproduce:
```
$ mkdir /tmp/builddir
$ ln -s /tmp/builddir build
$ cd build
$ cmake /path/to/wabt
```
With Make:
```
$ make
-- Configuring done
-- Generating done
-- Build files have been written to: /home/ericonr/docs/extpro/wabt/build
make[2]: *** No rule to make target '../src/apply-names.cc', nee... | Building inside a symlinked directory fails completely | https://api.github.com/repos/WebAssembly/wabt/issues/1607/comments | 6 | 2021-02-16T00:21:29Z | 2021-02-16T02:41:54Z | https://github.com/WebAssembly/wabt/issues/1607 | 808,892,577 | 1,607 |
[
"WebAssembly",
"wabt"
] | With the following WAT file, `ref.wat`:
```
(module
(func $a)
(func $b (ref.func $a) drop)
)
```
I run `wat2wasm --enable-all ref.wat` and receive an error:
```
ref.wat:3:22: error: function is not declared in any elem sections
(func $b (ref.func $a) drop)
^^
```
I did no... | wat2wasm fails to convert ref.func | https://api.github.com/repos/WebAssembly/wabt/issues/1606/comments | 1 | 2021-02-11T18:52:30Z | 2021-02-17T07:25:45Z | https://github.com/WebAssembly/wabt/issues/1606 | 806,652,386 | 1,606 |
[
"WebAssembly",
"wabt"
] | The new EH spec will eventually need to be supported in WABT. One new thing in the [update](https://github.com/WebAssembly/exception-handling/blob/1ec111eb32c8490991c943af2af40559dbd63cd4/proposals/exception-handling/Exceptions.md) is that the opcode for `catch_all` is 0x05, the same as `else`. This is not ambiguous be... | How to support the updated EH spec | https://api.github.com/repos/WebAssembly/wabt/issues/1604/comments | 8 | 2021-02-06T01:55:01Z | 2021-02-18T21:44:38Z | https://github.com/WebAssembly/wabt/issues/1604 | 802,580,970 | 1,604 |
[
"WebAssembly",
"wabt"
] | wasm-decompile fails to decompile the binary corresponding to the following code for instance:
```webassembly
(module
(func (result i32)
(block (result i32)
(i32.const 42)
(i32.const 1)
(br_if 1)
)
)
)
```
It fails with the following:
```wa... | wasm-decompile cannot handle branching out of a function | https://api.github.com/repos/WebAssembly/wabt/issues/1603/comments | 0 | 2021-02-05T21:08:12Z | 2021-02-05T21:12:08Z | https://github.com/WebAssembly/wabt/issues/1603 | 802,477,368 | 1,603 |
[
"WebAssembly",
"wabt"
] | Reproduction:
Look at this old Mozilla bug report: https://bugzilla.mozilla.org/show_bug.cgi?id=1409124 and take the [attached WebAssembly binary](https://bugzilla.mozilla.org/attachment.cgi?id=8918975).
Observe that the file is a minuscule 86 bytes.
Pass it through wasm2wat (without adding any extra debug informa... | Roundtripping Wasm through wasm2wat and wat2wasm adds bloat | https://api.github.com/repos/WebAssembly/wabt/issues/1601/comments | 4 | 2021-02-04T21:44:52Z | 2021-02-08T20:29:18Z | https://github.com/WebAssembly/wabt/issues/1601 | 801,658,331 | 1,601 |
[
"WebAssembly",
"wabt"
] | Hello! I ran into an issue with libwasm.dylib not working with the latest wasm.h when testing out some code I wrote against the Wasm C API so I tried to make a simple series of steps to reproduce it but found that wabt did not build with the updated wasm-c-api repo.
Steps to reproduce:
```shell
git submodule upd... | Wabt fails to build with latest wasm-c-api | https://api.github.com/repos/WebAssembly/wabt/issues/1600/comments | 0 | 2021-01-27T15:26:25Z | 2023-03-15T04:21:08Z | https://github.com/WebAssembly/wabt/issues/1600 | 795,199,464 | 1,600 |
[
"WebAssembly",
"wabt"
] | I have a problem in MAC, operation
cmake -- build .
thanks! | src/interp/interp-wasm-c-api.cc:17:10: fatal error: 'wasm.h' file not found | https://api.github.com/repos/WebAssembly/wabt/issues/1594/comments | 2 | 2020-12-24T01:17:06Z | 2024-06-26T02:41:38Z | https://github.com/WebAssembly/wabt/issues/1594 | 774,119,766 | 1,594 |
[
"WebAssembly",
"wabt"
] | Max allowed number of locals is `UINT32_MAX`, however WABT rejects it:
```sh
$ cat max_locals.wat
(module binary
"\00asm" "\01\00\00\00"
"\01\04\01\60\00\00" ;; Type section
"\03\02\01\00" ;; Function section
"\0a\0a\01" ;; Code section
;; function 0
... | Incorrect check for max allowed local count | https://api.github.com/repos/WebAssembly/wabt/issues/1593/comments | 1 | 2020-12-23T16:41:48Z | 2023-03-15T16:49:23Z | https://github.com/WebAssembly/wabt/issues/1593 | 773,924,487 | 1,593 |
[
"WebAssembly",
"wabt"
] | In particular, `DecompileExpr` calls itself recursively.
Example that fails: `clang -O2 quickjs.c -c` runs out of stack at VC++ default stack size of 1MB. | Decompiler can run out of stack space | https://api.github.com/repos/WebAssembly/wabt/issues/1591/comments | 1 | 2020-12-14T20:45:29Z | 2022-02-28T19:32:12Z | https://github.com/WebAssembly/wabt/issues/1591 | 766,911,881 | 1,591 |
[
"WebAssembly",
"wabt"
] | As per #1063 , there should probably be a CI setup for s390x (which works now that #1557 is merged), at least for catching regressions and stuff?
As far as we know that's something that needs to be done by the project maintainers, as it involves setting up hooks and whatnot. | Setup Travis CI (or equivalent) for big-endian (s390x)? | https://api.github.com/repos/WebAssembly/wabt/issues/1587/comments | 0 | 2020-12-07T22:15:53Z | 2020-12-07T22:15:53Z | https://github.com/WebAssembly/wabt/issues/1587 | 758,892,388 | 1,587 |
[
"WebAssembly",
"wabt"
] | They seem to be ignored:
```
(global (;15;) i32 (i32.const 172))
(global (;16;) i32 (i32.const 168))
(global (;17;) i32 (i32.const 2904))
(global (;18;) i32 (i32.const 3644))
``` | Names for globals from name section are not used in wasm2wat | https://api.github.com/repos/WebAssembly/wabt/issues/1584/comments | 3 | 2020-12-04T17:07:12Z | 2021-06-29T03:09:48Z | https://github.com/WebAssembly/wabt/issues/1584 | 757,258,163 | 1,584 |
[
"WebAssembly",
"wabt"
] | Hi there!
I'm currently importing wabt runtime by using wasm-c-api modules.
But I found that there are some missing api functions as follows.
#### Import api
* WASM_API_EXTERN own wasm_importtype_t* wasm_importtype_new(
own wasm_name_t* module, own wasm_name_t* name, own wasm_externtype_t*);
* WASM_API_EXTE... | Missing wasm-c-api functions | https://api.github.com/repos/WebAssembly/wabt/issues/1578/comments | 1 | 2020-12-02T08:07:16Z | 2021-01-12T02:50:45Z | https://github.com/WebAssembly/wabt/issues/1578 | 755,045,032 | 1,578 |
[
"WebAssembly",
"wabt"
] | The wat2wasm demo at https://webassembly.github.io/wabt/demo/wat2wasm allows the following code to compile (with flags):
```wat
(module
(func (export "selectTwo") (result i32 i32)
i32.const 0
i32.const 0
i32.const 0
i32.const 0
select (result i32 i32)
)
)
```
... | Demo allows compilation of multi-value select operation | https://api.github.com/repos/WebAssembly/wabt/issues/1577/comments | 4 | 2020-11-30T03:32:44Z | 2020-12-04T05:24:12Z | https://github.com/WebAssembly/wabt/issues/1577 | 753,112,256 | 1,577 |
[
"WebAssembly",
"wabt"
] | noticed while making a kotlin-writer: https://github.com/WebAssembly/wabt/blob/master/src/c-writer.cc#L1984 | wasm2c defines i64_load16_u but it's never used | https://api.github.com/repos/WebAssembly/wabt/issues/1575/comments | 0 | 2020-11-22T16:54:59Z | 2020-12-14T19:25:43Z | https://github.com/WebAssembly/wabt/issues/1575 | 748,284,707 | 1,575 |
[
"WebAssembly",
"wabt"
] | Hi,
I want to build all the tools in the release mode on Linux. I followed the instructions mentioned in the readme.md . but I am not able to get release version of binaries.
can someone help me | How to build wabt in release mode on Linux | https://api.github.com/repos/WebAssembly/wabt/issues/1571/comments | 11 | 2020-11-19T07:34:09Z | 2021-08-20T17:05:37Z | https://github.com/WebAssembly/wabt/issues/1571 | 746,326,649 | 1,571 |
[
"WebAssembly",
"wabt"
] | Currently we need to install Visual C++ Redistributable on Windows in order to run WABT, which is a slight inconvenience.
Could you link it statically?
I believe it is controlled by `-MT` and `-MTd` compiler fags and which are supported in CMake build via [MSVC_RUNTIME_LIBRARY](https://cmake.org/cmake/help/v3.19/... | Statically link Visual C++ runtime when releasing on Windows | https://api.github.com/repos/WebAssembly/wabt/issues/1568/comments | 1 | 2020-11-10T12:45:39Z | 2022-08-26T01:18:07Z | https://github.com/WebAssembly/wabt/issues/1568 | 739,879,403 | 1,568 |
[
"WebAssembly",
"wabt"
] | I'm using `wat2wasm`. The version is reported as `1.0.13 (1.0.19)` (I installed WABT with `brew`). I'm compiling handwritten WAT code.
If I load or store a (correctly aligned) 64-bit value with `align=3`, WABT incorrectly complains:
``` html
<location> error: alignment must be power-of-two
f64.load align=3
... | [wat2wasm] requires alignments be a power of two, which is incorrect | https://api.github.com/repos/WebAssembly/wabt/issues/1567/comments | 5 | 2020-11-10T01:18:52Z | 2020-11-11T18:41:05Z | https://github.com/WebAssembly/wabt/issues/1567 | 739,489,905 | 1,567 |
[
"WebAssembly",
"wabt"
] | # How to reproduce (and why this can be a problem)
Here is the minimum code to reproduce:
table-identifier.wat:
```wasm
(module
(import "js" "tbl" (table $tblImported 1 anyfunc))
(func $f (result i32) i32.const 42)
(elem $tblImported $f)
)
```
Running `wat2wasm table-identifier.wat` genera... | wat2wasm: elem without offset shouldn't be accepted | https://api.github.com/repos/WebAssembly/wabt/issues/1566/comments | 2 | 2020-11-09T06:35:51Z | 2020-11-11T17:43:41Z | https://github.com/WebAssembly/wabt/issues/1566 | 738,731,866 | 1,566 |
[
"WebAssembly",
"wabt"
] | some examples:
 | wasm-decompile outputs seemingly repetitive/nonsensical code | https://api.github.com/repos/WebAssembly/wabt/issues/1565/comments | 5 | 2020-11-04T07:11:25Z | 2021-04-26T23:33:30Z | https://github.com/WebAssembly/wabt/issues/1565 | 735,872,586 | 1,565 |
[
"WebAssembly",
"wabt"
] | Current problems:
- wasm sandbox interoperability is slow
- wasm can be written in different languages
So it will be useful to add one .wasm from another .wasm
Solution:
What if will try to disassemble .wasm -> .wat, contact table of functions as a string and assemble it back .wat -> .wasm? The problem wit... | wasm-concat ? | https://api.github.com/repos/WebAssembly/wabt/issues/1563/comments | 4 | 2020-10-28T06:59:33Z | 2022-09-18T06:38:03Z | https://github.com/WebAssembly/wabt/issues/1563 | 731,165,041 | 1,563 |
[
"WebAssembly",
"wabt"
] | We just upgraded from using 1.0.18 to 1.0.19; when builiding with GCC 10.2 on Linux, I get the following warnings that look concerning:
(only once:)
```
[79/3359] Building CXX object _deps/wabt-build/CMakeFiles/wabt.dir/src/binary-writer-spec.cc.o
In file included from _deps/wabt-src/src/binary-writer.h:20,
... | C++ warnings while compiling wabt 1.0.19 | https://api.github.com/repos/WebAssembly/wabt/issues/1562/comments | 3 | 2020-10-27T16:22:14Z | 2023-03-15T07:56:31Z | https://github.com/WebAssembly/wabt/issues/1562 | 730,605,661 | 1,562 |
[
"WebAssembly",
"wabt"
] | See the comments [here](https://github.com/WebAssembly/wabt/pull/1553#issuecomment-703713792) for background.
/cc @binji @aardappel | Fix func.wast failures with recent testsuite updates | https://api.github.com/repos/WebAssembly/wabt/issues/1561/comments | 1 | 2020-10-24T03:39:12Z | 2022-04-01T07:05:57Z | https://github.com/WebAssembly/wabt/issues/1561 | 728,648,849 | 1,561 |
[
"WebAssembly",
"wabt"
] | Trying to use the repo makefile just doesn't work. It's very inconsistent and different GNU make versions behave differently, and many tests fail when using it.
On 2 different systems, the makefile was not able to run the c-api examples. On a third system, it ran the tests instead of the examples, but the wat2wasm t... | Makefile behaves differently on different systems | https://api.github.com/repos/WebAssembly/wabt/issues/1558/comments | 1 | 2020-10-11T02:57:08Z | 2020-10-21T22:34:17Z | https://github.com/WebAssembly/wabt/issues/1558 | 718,745,457 | 1,558 |
[
"WebAssembly",
"wabt"
] | The binary reader reads types (functype, but also structs and arrays) in type section using signed LEB128 encoding. The spec defines type as single byte. This causing problem because WABT accepts longer sequences of bytes as valid types while there are invalid in the spec.
I can change the [`Type::Enum`](https://git... | Incorrect functype decoding | https://api.github.com/repos/WebAssembly/wabt/issues/1556/comments | 3 | 2020-10-02T10:59:20Z | 2022-09-18T06:42:50Z | https://github.com/WebAssembly/wabt/issues/1556 | 713,534,774 | 1,556 |
[
"WebAssembly",
"wabt"
] | See https://github.com/WebAssembly/wabt/pull/1549 for the kind of changes that need to happen. | Support --relocatable and multi-memory | https://api.github.com/repos/WebAssembly/wabt/issues/1552/comments | 2 | 2020-09-23T15:38:27Z | 2022-04-27T17:40:01Z | https://github.com/WebAssembly/wabt/issues/1552 | 707,474,611 | 1,552 |
[
"WebAssembly",
"wabt"
] | This looks to be related to https://github.com/WebAssembly/wabt/pull/1466
For the functions that define their type as `(type ...)` indices of local always start with 0:
```
$ cat type_sig.wast
(module
(type $sig (func (param i32) (result i32)))
(func (type $sig)
(local $var i32)
(local.get $var))
... | wat2wasm outputs incorrect local indices on function with type use | https://api.github.com/repos/WebAssembly/wabt/issues/1551/comments | 7 | 2020-09-23T15:18:55Z | 2020-11-10T20:35:43Z | https://github.com/WebAssembly/wabt/issues/1551 | 707,459,043 | 1,551 |
[
"WebAssembly",
"wabt"
] | We have been using WABT 1.0.12 interpreter as a baseline for our benchmarking while developing [Fizzy](https://github.com/wasmx/fizzy).
Recently we tried comparing WABT 1.0.12 against 1.0.19 on our benchmarks (mostly arithmetic-heavy code, crypto algos), and it showed significant slowdown in the latter (execution up... | Performance regression using new interpreter API | https://api.github.com/repos/WebAssembly/wabt/issues/1550/comments | 4 | 2020-09-23T10:02:35Z | 2020-10-21T22:43:44Z | https://github.com/WebAssembly/wabt/issues/1550 | 707,224,491 | 1,550 |
[
"WebAssembly",
"wabt"
] | For a while I've been working on a new library called wasp: https://github.com/binji/wasp. It has much of the same functionality as wabt, but written from the ground up to be a library rather than a suite of tools.
Wasp is now at the point where I'd like to look at incorporating it into wabt, so that features don't ... | Use wasp library in wabt | https://api.github.com/repos/WebAssembly/wabt/issues/1543/comments | 5 | 2020-09-11T19:17:22Z | 2024-01-30T09:44:21Z | https://github.com/WebAssembly/wabt/issues/1543 | 699,661,154 | 1,543 |
[
"WebAssembly",
"wabt"
] | Consider `c.wat`:
```wat
(module
(type (;0;) (func))
(import "env" "b" (func (;0;) (type 0)))
(func $a (type 0)
call 0)
(export "a" (func $a)))
```
If we `wat2wasm --relocatable` it and then `wasm-objdump -dx` it, we get:
```
...
Custom:
- name: "reloc.Code"
- relocations for section: 4... | Enabling bulk memory borks --relocatable | https://api.github.com/repos/WebAssembly/wabt/issues/1538/comments | 0 | 2020-09-09T13:57:22Z | 2020-09-16T22:22:46Z | https://github.com/WebAssembly/wabt/issues/1538 | 696,838,891 | 1,538 |
[
"WebAssembly",
"wabt"
] | Hi, The wasm-opcodecnt tool gives me the opcode count of whole binary file. But I wanted to know the opcode count for each function. Is there any way to get that info?
Ex:
```
(module
(type $t0 (func (param f64 f64) (result f64)))
(func $sum (type $t0) (param $p0 f64) (param $p1 f64) (result f64)
local.g... | Can we get opcode count for each function? | https://api.github.com/repos/WebAssembly/wabt/issues/1536/comments | 1 | 2020-09-09T04:21:25Z | 2020-09-10T17:55:43Z | https://github.com/WebAssembly/wabt/issues/1536 | 696,397,326 | 1,536 |
[
"WebAssembly",
"wabt"
] | Consider `a.c` which exports a function that calls something from `b.c`:
```
$ cat a.c
void b(void);
__attribute__((export_name("a"))) void a(void) { b(); }
$ cat b.c
void b(void) {}
```
With clang and wasm-ld, we can make a wasm file:
```
$ clang -Oz --target=wasm32 -nostdlib -c -o a.o a.c
$ clang -... | wat2wasm --relocatable should record exports in linking symtab | https://api.github.com/repos/WebAssembly/wabt/issues/1534/comments | 1 | 2020-09-08T09:19:02Z | 2020-09-10T17:13:38Z | https://github.com/WebAssembly/wabt/issues/1534 | 695,704,546 | 1,534 |
[
"WebAssembly",
"wabt"
] | I believe according to https://github.com/WebAssembly/memory64/blob/master/proposals/memory64/Overview.md#text-format the `i64` modifier is expected to come before the limits, but it looks like in the test added here in https://github.com/WebAssembly/wabt/pull/1500 have`i64` coming after the limits? | Memory64 text format parses `i64` in the wrong location | https://api.github.com/repos/WebAssembly/wabt/issues/1532/comments | 11 | 2020-09-02T20:47:44Z | 2021-08-13T00:04:38Z | https://github.com/WebAssembly/wabt/issues/1532 | 691,409,671 | 1,532 |
[
"WebAssembly",
"wabt"
] | This text file:
<details>
```wasm
(module
;; 64 random types to force the block type below to get encoded as sleb
(func (param f32 f32 f32 f32 f32 f32))
(func (param i32 f32 f32 f32 f32 f32))
(func (param f32 i32 f32 f32 f32 f32))
(func (param i32 i32 f32 f32 f32 f32))
(func (param f32 f32 i32 ... | Incorrect encoding of multi-value block types | https://api.github.com/repos/WebAssembly/wabt/issues/1531/comments | 1 | 2020-09-02T20:44:52Z | 2020-09-08T19:34:36Z | https://github.com/WebAssembly/wabt/issues/1531 | 691,407,732 | 1,531 |
[
"WebAssembly",
"wabt"
] | I followed the instructions in the README, and tried `make emcc-release`, `make emcc-debug`, and various other combinations. Nothing works. `No rule to make target 'emcc-release'`.
Everything works perfectly fine with gcc, and I can actually get it to start compiling using with emscripten if I follow the manual inst... | unable to build with emscripten | https://api.github.com/repos/WebAssembly/wabt/issues/1529/comments | 2 | 2020-08-28T14:08:35Z | 2020-08-29T00:41:10Z | https://github.com/WebAssembly/wabt/issues/1529 | 688,102,165 | 1,529 |
[
"WebAssembly",
"wabt"
] | When I clone your repository recursively, `mkdir build`, `cd build` and run `cmake ..`, I get this message printed 10s of times and then I get a `configuration failed` message:
```
System is unknown to cmake, create:
Platform/FreeBSD to use this system, please post your config file on discourse.cmake.org so it can b... | How can I run WABT on FreeBSD? | https://api.github.com/repos/WebAssembly/wabt/issues/1528/comments | 2 | 2020-08-26T12:49:03Z | 2020-09-03T19:05:50Z | https://github.com/WebAssembly/wabt/issues/1528 | 686,292,938 | 1,528 |
[
"WebAssembly",
"wabt"
] | PoC:
```
dwfault-mbp:~ dwfault$ hexdump PoC.wasm.objdump.1ff
0000000 00 61 73 6d 01 00 00 00 01 05 01 60 01 7f 00 03
0000010 03 02 00 00 05 03 01 00 00 07 16 03 03 6d 65 6d
0000020 02 00 04 6c 6f 57 64 00 [ff ff ff ff 0f] 1a 0b 0d
0000030 00 20 1c 02 86 80 80 80 00 02 ff ff ff ff 0f 1a
0000040 0b 0d 00 20 00 41... | wasm-objdump/wabt::ObjdumpNames::Set integer overflow after reading export items' index | https://api.github.com/repos/WebAssembly/wabt/issues/1520/comments | 1 | 2020-08-17T03:42:02Z | 2020-08-19T18:28:43Z | https://github.com/WebAssembly/wabt/issues/1520 | 679,910,440 | 1,520 |
[
"WebAssembly",
"wabt"
] | [PoC.wasm.zip](https://github.com/WebAssembly/wabt/files/5073300/PoC.wasm.zip)
Reproduced on git commit commit 2a15fcb, 2020.08.14(latest version).
This is null pointer reference because wasm-decompile cannot handle the situation when if branch is empty. Here's the stack trace:
```
* thread #1, queue = 'com.a... | wasm-decompile/wabt::Decompiler::DecompileExpr cannot handle when if branch is empty. | https://api.github.com/repos/WebAssembly/wabt/issues/1519/comments | 1 | 2020-08-14T08:09:07Z | 2023-01-03T19:29:48Z | https://github.com/WebAssembly/wabt/issues/1519 | 678,982,992 | 1,519 |
[
"WebAssembly",
"wabt"
] | [PoC.wasm.zip](https://github.com/WebAssembly/wabt/files/5072923/PoC.wasm.zip)
Reproduced on git commit commit 2a15fcb8ba45d43f6766bf76639b0071cd3a0913, 2020.08.14(latest version).
Here's the stack trace:
```
thread #1, queue = 'com.apple.main-thread', stop reason = EXC_BAD_ACCESS (code=2, address=0x6050000090... | wasm-decompile/wabt::AST::Construct cannot handle a specific stack unbalanced scenario result in a memory corruption. | https://api.github.com/repos/WebAssembly/wabt/issues/1518/comments | 2 | 2020-08-14T06:44:20Z | 2023-01-03T19:30:43Z | https://github.com/WebAssembly/wabt/issues/1518 | 678,940,819 | 1,518 |
[
"WebAssembly",
"wabt"
] | Getting this error when compiling our rust project. Have been unsuccessful in finding a workaround. Seems to be affecting all our machines running Ubuntu 18.04.
```
Caused by:
process didn't exit successfully: `/root/edgeware-node/target/release/build/wabt-sys-ff144c8369c2e02a/build-script-build` (exit code: 101)
... | Failing to compile wabt-sys 0.8.0 due to undeclared CMAKE_PROJECT_VERSION | https://api.github.com/repos/WebAssembly/wabt/issues/1514/comments | 5 | 2020-08-10T19:45:01Z | 2020-08-10T21:28:12Z | https://github.com/WebAssembly/wabt/issues/1514 | 676,372,323 | 1,514 |
[
"WebAssembly",
"wabt"
] | In the project README, under *Supported Proposals*, it lists the flags for the various proposals, and says the following:
* Proposal: Name and link to the WebAssembly proposal repo
* flag: Flag to pass to the tool to enable support for the feature
* binary: Whether wabt can read/write the binary format
* text: Wh... | Clarify how Supported Proposals work. | https://api.github.com/repos/WebAssembly/wabt/issues/1513/comments | 3 | 2020-08-10T02:17:39Z | 2020-08-11T23:59:58Z | https://github.com/WebAssembly/wabt/issues/1513 | 675,823,830 | 1,513 |
[
"WebAssembly",
"wabt"
] | I'm new to WASM, I just want to reverse a WASM program. I tried to compile the C code generated by wasm2c, but I got some errors:
```
/usr/bin/ld: /tmp/ccZq4O8u.o: in function `w2c_f20':
program.c:(.text+0x1698): undefined reference to `Z_envZ_boomZ_vii'
/usr/bin/ld: /tmp/ccZq4O8u.o: in function `w2c_f28':
program... | [wasm2c] C code is unable to compile, undefined reference to `WASI_xx` | https://api.github.com/repos/WebAssembly/wabt/issues/1510/comments | 3 | 2020-08-07T13:32:41Z | 2020-08-10T02:55:56Z | https://github.com/WebAssembly/wabt/issues/1510 | 675,019,188 | 1,510 |
[
"WebAssembly",
"wabt"
] | [wasm2c | https://api.github.com/repos/WebAssembly/wabt/issues/1509/comments | 0 | 2020-08-07T13:11:48Z | 2020-08-07T14:05:38Z | https://github.com/WebAssembly/wabt/issues/1509 | 675,006,586 | 1,509 | |
[
"WebAssembly",
"wabt"
] | Noticed by the binaryen fuzzer's wasm2c integration.
Background and testcase: https://github.com/WebAssembly/spec/issues/1224
Spec tests are added in https://github.com/WebAssembly/spec/pull/1225 | [wasm2c] Truncation of values slightly less than INT32_MIN is wrong | https://api.github.com/repos/WebAssembly/wabt/issues/1499/comments | 1 | 2020-07-27T19:51:44Z | 2022-04-27T17:53:09Z | https://github.com/WebAssembly/wabt/issues/1499 | 666,543,782 | 1,499 |
[
"WebAssembly",
"wabt"
] | ```
(module
(type $f_t (func (param $v i64) (result i64)))
(func $f (type $f_t) (get_local $v))
)
```
```
test.wat:3:35: error: undefined local variable "$v"
(func $f (type $f_t) (get_local $v))
```
`wat2wasm` currently doesn't accept that, and I don't know if it should.
I don't know if the WASM ... | Question: Should `local.get $v` work when `$v` is the name of a parameter declared via a separate type? | https://api.github.com/repos/WebAssembly/wabt/issues/1496/comments | 3 | 2020-07-23T08:23:05Z | 2020-07-25T10:48:09Z | https://github.com/WebAssembly/wabt/issues/1496 | 664,288,753 | 1,496 |
[
"WebAssembly",
"wabt"
] | When working with a small reftypes module:
```wasm
(module
(func
ref.null func
ref.is_null
drop))
```
I think that output of `wasm2wat` is missing a newline after the `ref.is_null`:
```
$ wat2wasm --enable-all foo.wat -o foo.wasm
$ wasm2wat --enable-all foo.wasm
(module
(type (;... | Missing newline after `ref.is_null` in `wasm2wat` | https://api.github.com/repos/WebAssembly/wabt/issues/1493/comments | 1 | 2020-07-21T22:36:06Z | 2020-09-02T20:52:23Z | https://github.com/WebAssembly/wabt/issues/1493 | 663,351,261 | 1,493 |
[
"WebAssembly",
"wabt"
] | The test located at [`test/desugar/locals.txt`](https://github.com/WebAssembly/wabt/blob/cd5ff133f84854f0b269f5cb06193ad8205f05d3/test/desugar/locals.txt) which looks like:
```wasm
(module
(type (func (param i32) (result i32)))
(func (type 0) (local $var i32)
(local.get 0)
(local.tee $var)))... | Numbering of `local.get` may not account for parameters | https://api.github.com/repos/WebAssembly/wabt/issues/1492/comments | 1 | 2020-07-21T22:33:13Z | 2020-09-02T20:51:20Z | https://github.com/WebAssembly/wabt/issues/1492 | 663,350,152 | 1,492 |
[
"WebAssembly",
"wabt"
] | The Readme in this repo suggests me to build the source code locally, but I prefer to use the system package manager to manage the tools, so that I can always upgrade to the latest version without checking the GitHub releases frequently.
I found wabt package in Ubuntu's apt and macOS's homebrew repository. After ins... | Is the wabt in system package managers officially supported? | https://api.github.com/repos/WebAssembly/wabt/issues/1490/comments | 3 | 2020-07-17T03:00:43Z | 2020-07-18T06:35:10Z | https://github.com/WebAssembly/wabt/issues/1490 | 658,788,360 | 1,490 |
[
"WebAssembly",
"wabt"
] | I'm getting a compilation error:
```
[ 80%] Building CXX object CMakeFiles/wasm.dir/src/interp/interp-wasm-c-api.cc.o
/usr/bin/c++ -DWASM_API_EXTERN="__attribute__((visibility(\"default\")))" -D__STDC_FORMAT_MACROS=1 -D__STDC_LIMIT_MACROS=1 -Dwasm_EXPORTS -I/builddir/build/BUILD/wabt-1.0.17 -I/builddir/build/BUILD/... | wabt 1.0.17 fails to compile on RHEL7 with gcc 4.8.5 | https://api.github.com/repos/WebAssembly/wabt/issues/1482/comments | 7 | 2020-07-15T13:41:35Z | 2022-09-18T05:35:47Z | https://github.com/WebAssembly/wabt/issues/1482 | 657,359,989 | 1,482 |
[
"WebAssembly",
"wabt"
] | When running 1.0.17 testsuite on ARMv7 32bit (Fedora 31), these tests fail:
```
- test/wasm2c/address-overflow.txt
- test/wasm2c/spec/address.txt
- test/wasm2c/spec/align.txt
- test/wasm2c/spec/binary-leb128.txt
- test/wasm2c/spec/binary.txt
- test/wasm2c/spec/br_if.txt
- test/wasm2c/spec/br_table.txt
- test... | multiple new test failures on ARMv7 32bit and x86 32bit | https://api.github.com/repos/WebAssembly/wabt/issues/1481/comments | 6 | 2020-07-15T10:04:51Z | 2022-02-08T09:17:00Z | https://github.com/WebAssembly/wabt/issues/1481 | 657,228,015 | 1,481 |
[
"WebAssembly",
"wabt"
] | I'm not sure why it sometimes does and sometimes doesn't... the flakiness is preventing me from reducing the testcase.
STR:
```
clang main.c wasm.c $WABT/wasm2c/wasm-rt-impl.c -I$WABT/wasm2c -lm -g -DWASM_RT_MEMCHECK_SIGNAL_HANDLER=1
```
Running that, it segfaults as it tries to load from an invalid address,
``... | wasm2c: signal handler doesn't always work (linux) | https://api.github.com/repos/WebAssembly/wabt/issues/1478/comments | 3 | 2020-07-10T19:36:34Z | 2020-07-14T00:16:34Z | https://github.com/WebAssembly/wabt/issues/1478 | 654,995,004 | 1,478 |
[
"WebAssembly",
"wabt"
] | Using `wat2wasm --enable-gc` on the current WASM GC branch (https://github.com/WebAssembly/wabt/tree/19e51dbb3ccd2e1586f7aeb49f2f0f0c78169423), I get these errors:
```
problem.wat:11:4: error: type mismatch in local.set, expected [ref 1] but got [ref 0]
(local.set $new_obj)
^^^^^^^^^
problem.wat:13:4: error: ... | GC branch: wat2wasm errors with order of local variables of struct or array reference type | https://api.github.com/repos/WebAssembly/wabt/issues/1477/comments | 0 | 2020-06-29T07:42:35Z | 2020-06-30T17:58:07Z | https://github.com/WebAssembly/wabt/issues/1477 | 647,191,611 | 1,477 |
[
"WebAssembly",
"wabt"
] | I have this function `(import "socket" "core.create_socket" (func $std/socket/core.create_socket (result i32)))` in my wat file but it get converted to `extern u32 (*Z_socketZ_coreZ2Ecreate_socketZ_iv)(void);` or I would expect `extern s32 (*Z_socketZ_coreZ2Ecreate_socketZ_iv)(void);`.
Shouldn't wasm `i32` become `s... | Why i32 got convert to u32? | https://api.github.com/repos/WebAssembly/wabt/issues/1476/comments | 3 | 2020-06-26T16:46:25Z | 2020-06-29T19:24:43Z | https://github.com/WebAssembly/wabt/issues/1476 | 646,385,203 | 1,476 |
[
"WebAssembly",
"wabt"
] | 
what happened ?
is bug?
| mac build is errr | https://api.github.com/repos/WebAssembly/wabt/issues/1475/comments | 1 | 2020-06-24T02:09:43Z | 2022-05-19T01:11:42Z | https://github.com/WebAssembly/wabt/issues/1475 | 644,263,232 | 1,475 |
[
"WebAssembly",
"wabt"
] | When I am running the [example](https://github.com/WebAssembly/wabt/tree/master/wasm2c/examples/fac) in wasm2c, I am getting a warning:
```sh
wasm-rt-impl.c: In function ‘wasm_rt_allocate_memory’:
wasm-rt-impl.c:134:12: warning: comparison between pointer and integer
if (addr == -1) {
^~
```
`... | warning: comparison between pointer and integer | https://api.github.com/repos/WebAssembly/wabt/issues/1472/comments | 1 | 2020-06-21T08:09:03Z | 2020-06-22T17:23:33Z | https://github.com/WebAssembly/wabt/issues/1472 | 642,517,832 | 1,472 |
[
"WebAssembly",
"wabt"
] | With the version 1.0.17 I receive the follow errors on the travis build system. Any ideas what are the cause? The version 1.0.15 has work without problems. Are there changed system requirements? For a full log see at: https://api.travis-ci.org/v3/job/699849563/log.txt
```
/tmp/wabt/wabt-1.0.17/share/man/man1/wat2wasm... | wat2wasm not working under Linux | https://api.github.com/repos/WebAssembly/wabt/issues/1470/comments | 1 | 2020-06-18T20:28:49Z | 2020-06-18T20:33:33Z | https://github.com/WebAssembly/wabt/issues/1470 | 641,529,143 | 1,470 |
[
"WebAssembly",
"wabt"
] | What is the status of the GC features? With version 1.0.17 I try:
```
(module
(func $test(local $val eqref)
)
)
```
I receive `error: unexpected token "eqref", expected i32, i64, f32, f64, v128 or externref.` | Support for eqref an other features of the GC MVP | https://api.github.com/repos/WebAssembly/wabt/issues/1469/comments | 2 | 2020-06-18T19:51:14Z | 2022-03-13T22:54:33Z | https://github.com/WebAssembly/wabt/issues/1469 | 641,509,325 | 1,469 |
[
"WebAssembly",
"wabt"
] | I was wondering how important is performance to the WABT project, in particular the performance of the interpreter? Is it something that the project should actively try to improve upon?
While working on [wasmjit-omr](https://github.com/wasmjit-omr/wasmjit-omr) [1], we found that we could improve overall performanc... | Performance of WABT Interpreter | https://api.github.com/repos/WebAssembly/wabt/issues/1465/comments | 2 | 2020-06-15T19:28:07Z | 2022-09-18T06:44:42Z | https://github.com/WebAssembly/wabt/issues/1465 | 639,086,764 | 1,465 |
[
"WebAssembly",
"wabt"
] | Consider this example:
```
$ cat module0.wat
(module
(type (func (param i32) (result i32)))
(func (type 0) (local $var i32)
(local.get 0)
(local.tee $var)))
$ wat-desugar module0.wat
(module
(type (;0;) (func (param i32) (result i32)))
(func (;0;) (type 0) (param $var i32) (result i... | Desugar confuses named variables | https://api.github.com/repos/WebAssembly/wabt/issues/1464/comments | 1 | 2020-06-13T18:17:42Z | 2020-06-17T12:59:51Z | https://github.com/WebAssembly/wabt/issues/1464 | 638,207,396 | 1,464 |
[
"WebAssembly",
"wabt"
] | The printed version is wrong. If I call `wat2wasm.exe --version` then download release 1.0.15 print
`1.0.13 (1.0.14)`
If I build the trunk version then it print
`1.0.13 (gh-actions-test2)`
Sounds like the version was never incremented. | Version is wrong | https://api.github.com/repos/WebAssembly/wabt/issues/1463/comments | 4 | 2020-06-13T15:00:03Z | 2021-08-29T10:21:07Z | https://github.com/WebAssembly/wabt/issues/1463 | 638,176,534 | 1,463 |
[
"WebAssembly",
"wabt"
] |
```wasm
(module )
(input "a.wasm")
```
Calling `wast2json` on the above `wast` test produces this message:
```
a.wast:2:1: error: unexpected token (, expected EOF.
(input "a.wasm")
^
```
The same test is valid according to the spec interpreter.
Finding out what's going on took me quite some time. Your ... | Confusing error for input instruction | https://api.github.com/repos/WebAssembly/wabt/issues/1459/comments | 0 | 2020-06-10T11:20:41Z | 2020-06-10T17:46:11Z | https://github.com/WebAssembly/wabt/issues/1459 | 636,164,550 | 1,459 |
[
"WebAssembly",
"wabt"
] | AFAICT there are no tests for libwasm -- it's hard to expect external projects to rely on using it without any. Are there plans to add any? (Alternately, plans to have wasm-interp use it instead of the existing api?) | libwasm needs tests | https://api.github.com/repos/WebAssembly/wabt/issues/1458/comments | 1 | 2020-06-10T02:02:43Z | 2020-06-10T17:44:56Z | https://github.com/WebAssembly/wabt/issues/1458 | 635,870,172 | 1,458 |
[
"WebAssembly",
"wabt"
] | At least some of the public API defined by https://github.com/WebAssembly/wasm-c-api appears to be unimplemented. I found wasm_importtype_name() and wasm_module_imports() to be missing, but I didn't check for others. | interp-wasm-c-api is incomplete | https://api.github.com/repos/WebAssembly/wabt/issues/1457/comments | 1 | 2020-06-10T01:48:51Z | 2020-06-17T23:22:36Z | https://github.com/WebAssembly/wabt/issues/1457 | 635,865,990 | 1,457 |
[
"WebAssembly",
"wabt"
] | Hi,
During fuzzing I found that the following module was consider invalid by wabt due to a `leb128` parsing error. Binaryen choose to "reject" this module but precise that it is a valid module. Other tools like [wasmer](https://github.com/wasmerio/wasmer), [wasmtime](https://github.com/bytecodealliance/wasmtime) and... | [wasm2wat] Incorrect rejection of valid module | https://api.github.com/repos/WebAssembly/wabt/issues/1455/comments | 2 | 2020-06-09T08:25:06Z | 2020-06-17T01:12:05Z | https://github.com/WebAssembly/wabt/issues/1455 | 635,217,841 | 1,455 |
[
"WebAssembly",
"wabt"
] | Hi,
During fuzzing I found that the following module was consider valid by `wabt` but rejected by some other tools like `binaryen` and `wasmtime`.
### Reproducing
Download: [not_valid_wabt.zip](https://github.com/WebAssembly/wabt/files/4746708/not_valid_wabt.zip)
``` sh
$ ./wasm-validate not_valid_wabt.was... | [bug] Incorrect validation of module with malformed alignment by wabt | https://api.github.com/repos/WebAssembly/wabt/issues/1453/comments | 0 | 2020-06-08T15:06:24Z | 2020-06-09T15:51:06Z | https://github.com/WebAssembly/wabt/issues/1453 | 634,703,018 | 1,453 |
[
"WebAssembly",
"wabt"
] | As title.
Windows zip archive only contains .exe files.
There's no library for us to link third party wasm-c-api apps against. | wabt (as of 1.0.15) doesn't ship libraries in precompiled distributions | https://api.github.com/repos/WebAssembly/wabt/issues/1452/comments | 2 | 2020-06-07T12:45:42Z | 2020-06-10T23:58:18Z | https://github.com/WebAssembly/wabt/issues/1452 | 633,383,453 | 1,452 |
[
"WebAssembly",
"wabt"
] | Given this input:
```
(module
(table $t 10 funcref)
(elem declare funcref (ref.func $f) (ref.func $f) (ref.null func) (ref.func $g))
(func $f)
(func $g)
)
```
this round trips as:
```
$ wat2wasm foo.wat -o foo.wasm --enable-all
$ wasm2wat foo.wasm --enable-all
(module
(type (;0;) (func))
... | wasm2wat: Missing `declare` on elem segments with expressions | https://api.github.com/repos/WebAssembly/wabt/issues/1449/comments | 1 | 2020-05-29T15:37:08Z | 2020-05-29T20:34:59Z | https://github.com/WebAssembly/wabt/issues/1449 | 627,356,861 | 1,449 |
[
"WebAssembly",
"wabt"
] | Given this input:
```wasm
(module
(table (import "Mtable_ex" "t-func") 1 funcref)
(table (import "Mtable_ex" "t-extern") 1 externref)
)
```
it round trips as:
```
$ wat2wasm foo.wat -o foo.wasm --enable-all
$ wasm2wat foo.wasm
(module
(import "Mtable_ex" "t-func" (table (;0;) 1 funcref))
(imp... | wasm2wat: Incorrect table type printed for imported externref tables | https://api.github.com/repos/WebAssembly/wabt/issues/1448/comments | 0 | 2020-05-29T15:32:35Z | 2020-05-29T20:34:47Z | https://github.com/WebAssembly/wabt/issues/1448 | 627,354,143 | 1,448 |
Subsets and Splits
Unique Owner-Repo Count
Counts the number of unique owner-repos in the dataset, providing a basic understanding of diverse repositories.