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.46B | issue_number int64 1 127k |
|---|---|---|---|---|---|---|---|---|---|
[
"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 |
[
"WebAssembly",
"wabt"
] | This is unfortunately a bit of a difficult issue to reproduce, but the gist of the issue is that `wasm2wat` will normalize an elem segment when printing, so the text format isn't necessarily faithful to how the binary format was written down.
The general idea is with an element segment that looks like `(elem (;0;) f... | wasm2wat normalizes element segments when printing | https://api.github.com/repos/WebAssembly/wabt/issues/1447/comments | 1 | 2020-05-29T15:27:56Z | 2020-05-29T17:59:18Z | https://github.com/WebAssembly/wabt/issues/1447 | 627,351,258 | 1,447 |
[
"WebAssembly",
"wabt"
] | Given this input wat:
```wasm
(module $n
(table $t 0 funcref)
(table $u 0 funcref)
(elem $e 0)
(func
i32.const 0
i32.const 0
i32.const 0
table.copy $t $u)
(func
i32.const 0
i32.const 0
i32.const 0
table.init $u $e)
)
```
this prints out as:
```
$ wat... | wasm2wat: table.init and table.copy don't print table indices | https://api.github.com/repos/WebAssembly/wabt/issues/1445/comments | 0 | 2020-05-28T19:58:32Z | 2020-05-29T00:03:37Z | https://github.com/WebAssembly/wabt/issues/1445 | 626,775,588 | 1,445 |
[
"WebAssembly",
"wabt"
] | This input wat file:
```wasm
(module
(func
ref.null func
ref.null func
i32.const 0
select (result funcref)
drop
)
)
```
will succesfully get encoded in wasm, but when it comes back out it's printed with the wrong `select` instruction:
```
$ wat2wasm foo.wat -o foo.wasm --enab... | wasm2wat loses type information on `select` instruction (reference types) | https://api.github.com/repos/WebAssembly/wabt/issues/1444/comments | 0 | 2020-05-28T19:55:02Z | 2020-05-29T19:46:55Z | https://github.com/WebAssembly/wabt/issues/1444 | 626,773,581 | 1,444 |
[
"WebAssembly",
"wabt"
] | Currently it looks like `wasm2wat` doesn't print the table index for element segments if they're active on a nonzero table. For example with this input:
```wat
(module
(table 1 funcref)
(table 1 funcref)
(elem (table 1) (i32.const 0) 0)
(func)
)
```
will print:
```
$ wat2wasm foo.wat --enable-a... | `wasm2wat` doesn't print nonzero table indices | https://api.github.com/repos/WebAssembly/wabt/issues/1443/comments | 0 | 2020-05-28T19:40:17Z | 2020-05-29T00:03:37Z | https://github.com/WebAssembly/wabt/issues/1443 | 626,765,432 | 1,443 |
[
"WebAssembly",
"wabt"
] | Link to wasm-decompile on main page 404s | https://api.github.com/repos/WebAssembly/wabt/issues/1441/comments | 1 | 2020-05-27T22:41:12Z | 2020-05-27T22:41:41Z | https://github.com/WebAssembly/wabt/issues/1441 | 626,083,174 | 1,441 | |
[
"WebAssembly",
"wabt"
] | Most Wasm engines use the CPU's hardware memory protection to handle wasm sandboxing; since wasm32 pointers are 32-bit, we can reserve 8GiB (33-bits, 32-bit index plus 32-bit offset) of address space for each memory object. All addresses outside the valid range will trap in the OS, which then can be handled and convert... | [wasm2c] Add support for trap-handling memory sandboxing | https://api.github.com/repos/WebAssembly/wabt/issues/1440/comments | 1 | 2020-05-26T20:22:09Z | 2022-05-19T01:15:21Z | https://github.com/WebAssembly/wabt/issues/1440 | 625,173,930 | 1,440 |
[
"WebAssembly",
"wabt"
] | relates to https://github.com/Homebrew/homebrew-core/pull/55046
Just want to point out that the prerelease tag failed the homebrew audit check, let me know if that is intentional. Thanks! | prelease blocking the homebrew formula upgrade | https://api.github.com/repos/WebAssembly/wabt/issues/1439/comments | 13 | 2020-05-26T17:11:18Z | 2020-08-10T13:39:31Z | https://github.com/WebAssembly/wabt/issues/1439 | 625,045,188 | 1,439 |
[
"WebAssembly",
"wabt"
] | As mentioned in #1436 I need an npm package for wasm2c (basically I want to use it from emscripten, and an emscripten build is the easiest and best way to get one!)
I created a quick one now: https://www.npmjs.com/package/wasm2c it basically has my build and the wasm2c runtime sources.
cc @dcodeIO @binji - thoug... | npm packaging of wasm2c | https://api.github.com/repos/WebAssembly/wabt/issues/1438/comments | 6 | 2020-05-21T22:42:32Z | 2022-05-19T01:17:56Z | https://github.com/WebAssembly/wabt/issues/1438 | 622,834,129 | 1,438 |
[
"WebAssembly",
"wabt"
] | While working on an issue in Wasmer, we realized that wabt was unable to parse/validate a valid Wasm file, failing with a `needed_dynlibs` error (my local wabt was installed via homebrew).
```bash
$ wasm2wat lib/c-api/tests/assets/hello_wasm.wasm
0000018: error: unable to read u32 leb128: needed_dynlibs
```
``... | wasm2wat needed_dynlibs error | https://api.github.com/repos/WebAssembly/wabt/issues/1429/comments | 6 | 2020-05-16T07:49:47Z | 2020-05-19T05:08:09Z | https://github.com/WebAssembly/wabt/issues/1429 | 619,407,101 | 1,429 |
[
"WebAssembly",
"wabt"
] | On main page: https://github.com/WebAssembly/wabt the link to wasm-decompile doc is broken https://webassembly.github.io/wabt/doc/wasm-decompile.1.html
I think it is missing from https://github.com/WebAssembly/wabt/tree/master/docs/doc | wasm-decompile link in README is broken | https://api.github.com/repos/WebAssembly/wabt/issues/1428/comments | 5 | 2020-05-15T23:26:21Z | 2022-09-18T06:03:09Z | https://github.com/WebAssembly/wabt/issues/1428 | 619,323,348 | 1,428 |
[
"WebAssembly",
"wabt"
] | Right now compiling a wasm with a function called `main` leads to clang complaining about
```cpp
static u32 main(u32, u32);
static u32 main(u32, u32) {
.. impl ..
}
```
```cpp
a.c:179:1: warning: 'main' should not be declared static [-Wmain]
static u32 main(u32, u32);
^~~~~~~
a.c:179:8: warning: return... | wasm2c: function name mangling? | https://api.github.com/repos/WebAssembly/wabt/issues/1426/comments | 2 | 2020-05-15T14:08:17Z | 2020-05-15T20:50:37Z | https://github.com/WebAssembly/wabt/issues/1426 | 618,993,807 | 1,426 |
[
"WebAssembly",
"wabt"
] | Noticed this [here](https://github.com/AssemblyScript/wabt.js/pull/15) while attempting to update the wabt.js buildbot to GitHub Actions and decided to test with all of fastcomp, upstream and tot because why not.
Tracked this down so far to `Module._malloc` for example trying to call into `Module['asm']['ya']`, whic... | libwabt.js builds are broken with Emscripten upstream/tot | https://api.github.com/repos/WebAssembly/wabt/issues/1421/comments | 3 | 2020-05-12T19:53:56Z | 2020-05-13T15:17:56Z | https://github.com/WebAssembly/wabt/issues/1421 | 616,918,122 | 1,421 |
[
"WebAssembly",
"wabt"
] | On one hand there is the Readme.md providing information for cloning and building the suite manually.
On the other hand there are binaries packed in archives for different platforms provided on the 'releases' tab, which is very helpful for beginners.
What I am missing though, are instructions for what to do after u... | Missing instructions for the provided binary archives | https://api.github.com/repos/WebAssembly/wabt/issues/1420/comments | 3 | 2020-05-12T18:30:48Z | 2020-05-13T19:42:05Z | https://github.com/WebAssembly/wabt/issues/1420 | 616,868,815 | 1,420 |
[
"WebAssembly",
"wabt"
] | Given an input such as:
```wasm
(module (func (param i32) (param $b i32)))
```
This round-trip through tooling fails to succeed:
```
$ wat2wasm --debug-names foo.wat -o foo.wasm
$ wasm2wat foo.wasm > bar.wat
$ wat2wasm bar.wat -o bar.wasm
bar.wat:3:35: error: unexpected token $b, expected ).
(func (;... | `wasm2wat` may produce un-parseable WAT syntax with parameter names | https://api.github.com/repos/WebAssembly/wabt/issues/1417/comments | 2 | 2020-05-11T20:01:17Z | 2020-05-14T18:39:07Z | https://github.com/WebAssembly/wabt/issues/1417 | 616,145,794 | 1,417 |
[
"WebAssembly",
"wabt"
] | Hey,
Similar assertion failure than #1413 but in another expression.
```
Assertion `sig_index < module_->types.size()' failed.
```
Related code (line `737`):
https://github.com/WebAssembly/wabt/blob/e88bc660cf89ca84dccda358cfbadc8a7c2bc935/src/binary-reader-ir.cc#L736-L738
# Reproducing
Download: [asser... | [wasm2wat] Assertion failure in BinaryReaderIR::OnReturnCallIndirectExpr | https://api.github.com/repos/WebAssembly/wabt/issues/1414/comments | 1 | 2020-05-10T17:05:05Z | 2020-06-09T08:41:40Z | https://github.com/WebAssembly/wabt/issues/1414 | 615,433,760 | 1,414 |
[
"WebAssembly",
"wabt"
] | Hey,
During fuzzing I triggered this assertion failure using `wasm2wat --enable-all`:
```
Assertion `sig_index < module_->types.size()' failed.
```
Related code (line `725`):
https://github.com/WebAssembly/wabt/blob/e88bc660cf89ca84dccda358cfbadc8a7c2bc935/src/binary-reader-ir.cc#L724-L726
# Reproducing
... | [wasm2wat] Assertion failure in BinaryReaderIR::OnCallIndirectExpr | https://api.github.com/repos/WebAssembly/wabt/issues/1413/comments | 1 | 2020-05-10T17:00:06Z | 2020-06-09T08:40:51Z | https://github.com/WebAssembly/wabt/issues/1413 | 615,432,882 | 1,413 |
[
"WebAssembly",
"wabt"
] | Seems like adding a dependency on https://github.com/cjihrig/uvwasi might be a good start. | Add WASI API to wasm-interp / wasm2c | https://api.github.com/repos/WebAssembly/wabt/issues/1409/comments | 2 | 2020-05-10T00:21:57Z | 2020-05-13T01:28:44Z | https://github.com/WebAssembly/wabt/issues/1409 | 615,286,250 | 1,409 |
[
"WebAssembly",
"wabt"
] | `wasm-decompile.exe` tool is great!!! It gives better readable format.
Is it possible to have the mangled function name instead of demangled in the output file ?
| Is it possible to have de-mangled function name in the output of wasm-decompile.exe | https://api.github.com/repos/WebAssembly/wabt/issues/1406/comments | 13 | 2020-05-06T01:47:52Z | 2023-01-03T19:30:11Z | https://github.com/WebAssembly/wabt/issues/1406 | 612,998,200 | 1,406 |
[
"WebAssembly",
"wabt"
] | When `wast2json` is run on the upstream annotations proposal test it currently infinite loops:
```
$ wast2json testsuite/proposals/annotations/annotations.wast --enable-all
<hangs>
```
I've minimized this to:
```wat
(module quote "(@a \0a)") ;; \n
```
where `wast2json` run over that file infinite loop... | Infinite loop parsing upstream annotations proposal | https://api.github.com/repos/WebAssembly/wabt/issues/1404/comments | 1 | 2020-05-05T14:35:22Z | 2020-05-06T18:48:15Z | https://github.com/WebAssembly/wabt/issues/1404 | 612,651,834 | 1,404 |
[
"WebAssembly",
"wabt"
] | Hi,
I want to use clang to compile the c file generated by wasm2c into LLVM IR.
The command I used is as follows:
`clang -emit-llvm -c test.c -I ~/wabt/wasm2c/`
However it fails and I got some errors listed below:
```
error: static declaration of '__signbitl' follows non-static declaration
error: too man... | Compile test.c (generated by wasm2c) into LLVM | https://api.github.com/repos/WebAssembly/wabt/issues/1402/comments | 2 | 2020-05-01T14:39:19Z | 2022-04-27T17:57:23Z | https://github.com/WebAssembly/wabt/issues/1402 | 610,784,282 | 1,402 |
[
"WebAssembly",
"wabt"
] | Fuzz testcase:
```wat
(module
(type $none_=>_none (func))
(memory $0 1 1)
(global $global$0 (mut i32) (i32.const 10))
(export "hangLimitInitializer" (func $1))
(export "func_13_invoker" (func $0))
(func $0
(loop $label$1
(if
(global.get $global$0)
(block
(global.set $global$0
... | wasm2c load/store offset calculation | https://api.github.com/repos/WebAssembly/wabt/issues/1400/comments | 5 | 2020-04-28T16:06:21Z | 2020-04-29T15:29:41Z | https://github.com/WebAssembly/wabt/issues/1400 | 608,436,825 | 1,400 |
[
"WebAssembly",
"wabt"
] | For the input file
```
(module quote "")
```
wast2json 1.0.13 crashes:
```
$ wast2json malformed.wast --no-check
wast2json: /home/andrei/dev/wabt/src/wast-parser.cc:474: wabt::Token wabt::WastParser::Consume(): Assertion `!tokens_.empty()' failed.
Aborted (core dumped)
``` | wast2json assertion failure when file contains malformed module | https://api.github.com/repos/WebAssembly/wabt/issues/1399/comments | 0 | 2020-04-28T11:04:55Z | 2020-04-28T11:04:55Z | https://github.com/WebAssembly/wabt/issues/1399 | 608,228,514 | 1,399 |
[
"WebAssembly",
"wabt"
] | I've compiled a simple example with Clang 8.0.1:
```c
int f() {
return 42;
}
```
With latest wabt release (1.0.13), wasm2wat dump for this file is:
```wat
(module
(type (;0;) (func))
(func $__wasm_call_ctors (type 0))
(table (;0;) 1 1 funcref)
(memory (;0;) 2)
(global (;0;) (mut i32) (i32.... | wasm-decompile doesn't mark standard exported globals as exported | https://api.github.com/repos/WebAssembly/wabt/issues/1397/comments | 1 | 2020-04-27T18:03:47Z | 2023-01-03T19:30:27Z | https://github.com/WebAssembly/wabt/issues/1397 | 607,743,366 | 1,397 |
[
"WebAssembly",
"wabt"
] | I tried to decompile a Wasm file that contains SIMD instructions to Wat and got this error:
```
Error: readWasm failed:
0000039: error: expected valid local type
``` | wasm2wat crashes upon reaching SIMD instructions | https://api.github.com/repos/WebAssembly/wabt/issues/1396/comments | 12 | 2020-04-27T04:51:59Z | 2020-04-28T02:10:30Z | https://github.com/WebAssembly/wabt/issues/1396 | 607,231,333 | 1,396 |
[
"WebAssembly",
"wabt"
] | I tried to build the gc branch using CMake directly, as described in the README.
The build fails with
```
In file included from /[..]/wabt/src/shared-validator.cc:17:
/[..]/wabt/src/shared-validator.h:194:47:
error: ‘MutVector’ does not name a type; did you mean ‘VarVector’?
194 | StructType(const TypeVec... | Failing to compile GC branch | https://api.github.com/repos/WebAssembly/wabt/issues/1395/comments | 2 | 2020-04-25T15:31:42Z | 2020-05-24T14:25:51Z | https://github.com/WebAssembly/wabt/issues/1395 | 606,793,930 | 1,395 |
[
"WebAssembly",
"wabt"
] | I think wasm should have a framework that all browsers use. It should contain
- all the common numeric, literal and date type operations and casting.
- Dom manipulation operations.
- sending requests to the server if needs (like Ajax).
Isn't this all what we need from client code?
If this wasm framework contai... | Can we have a wasm framework? | https://api.github.com/repos/WebAssembly/wabt/issues/1394/comments | 1 | 2020-04-23T17:16:45Z | 2020-04-24T00:02:27Z | https://github.com/WebAssembly/wabt/issues/1394 | 605,707,635 | 1,394 |
[
"WebAssembly",
"wabt"
] | The "Legacy active, funcref elemexpr" element segment (flag = 4) is not supported in wat2wasm.
It is however supported in wasm2wat. | The "Legacy active, funcref elemexpr" element segment not supported in wat2wasm. | https://api.github.com/repos/WebAssembly/wabt/issues/1391/comments | 3 | 2020-04-15T19:12:45Z | 2020-04-16T18:05:12Z | https://github.com/WebAssembly/wabt/issues/1391 | 600,526,951 | 1,391 |
[
"WebAssembly",
"wabt"
] | The proposal document describes the opcode for v8x16.shuffle as 0xfd 0xc1,
The wabt tools however use the code 0xfd 0x03.
Which one is rightt? | Wrong opcode for v8x16.shuffle? | https://api.github.com/repos/WebAssembly/wabt/issues/1390/comments | 2 | 2020-04-15T19:08:11Z | 2020-04-15T20:38:35Z | https://github.com/WebAssembly/wabt/issues/1390 | 600,524,299 | 1,390 |
[
"WebAssembly",
"wabt"
] | If try to compile the follow sample code with the command line: `wat2wasm.exe --enable-all sample.wat`
```
(module
(func $test(local $exn exnref)
try
i32.const 0
drop
catch
local.tee $exn
drop
end
)
)
```
then I receive the error:
```
sample.... | locals of type exnref | https://api.github.com/repos/WebAssembly/wabt/issues/1388/comments | 2 | 2020-04-13T13:41:31Z | 2020-04-17T17:18:24Z | https://github.com/WebAssembly/wabt/issues/1388 | 598,896,263 | 1,388 |
[
"WebAssembly",
"wabt"
] | Hi,
During fuzzing I found this vulnerability inside `wabt::BinaryReader`.
Based on quick analysis using GDB, valgrind and ASAN, it seems to be a uncontrolled memory allocation vulnerability ([CWE-789](https://cwe.mitre.org/data/definitions/789.html)) which generates a `std::bad_alloc` exception and finally allow... | [crash] SIGABRT due to std::bad_alloc exception (resizing wasm br_table) | https://api.github.com/repos/WebAssembly/wabt/issues/1386/comments | 0 | 2020-04-12T10:42:13Z | 2020-05-13T22:27:33Z | https://github.com/WebAssembly/wabt/issues/1386 | 598,457,049 | 1,386 |
[
"WebAssembly",
"wabt"
] | The current build requires python 3.5, which is commonly found on modern *nixes, but may not be installed on Windows, Mac, etc. It's only used for running tests, so it would be nice to fail gracefully if python isn't available instead of preventing the build to proceed. | Don't require Python in build (if not found, skip those targets) | https://api.github.com/repos/WebAssembly/wabt/issues/1385/comments | 12 | 2020-04-09T19:43:22Z | 2022-08-26T02:15:19Z | https://github.com/WebAssembly/wabt/issues/1385 | 597,510,787 | 1,385 |
[
"WebAssembly",
"wabt"
] | I would be nice to get https://github.com/WebAssembly/simd/pull/197 into wabt. Though this seems to require the proposals test suite to be updated upstream first. @sbc100 ?
| Update to more recent test suite | https://api.github.com/repos/WebAssembly/wabt/issues/1379/comments | 3 | 2020-03-26T14:21:36Z | 2020-03-27T21:50:56Z | https://github.com/WebAssembly/wabt/issues/1379 | 588,458,660 | 1,379 |
[
"WebAssembly",
"wabt"
] | The exception proposal is currently supported for binary/text reading/writing and validation, but has no support in the interpreter.
Now that the interpreter has a garbage collector, it should be possible to implement this. | Implement exception proposal support in interpreter | https://api.github.com/repos/WebAssembly/wabt/issues/1378/comments | 1 | 2020-03-25T23:11:41Z | 2022-04-27T17:58:27Z | https://github.com/WebAssembly/wabt/issues/1378 | 588,046,295 | 1,378 |
[
"WebAssembly",
"wabt"
] | See https://github.com/webassembly/function-references and https://github.com/WebAssembly/function-references/blob/master/proposals/function-references/Overview.md. | Implement function-references proposal | https://api.github.com/repos/WebAssembly/wabt/issues/1377/comments | 1 | 2020-03-25T23:09:12Z | 2021-07-08T11:16:47Z | https://github.com/WebAssembly/wabt/issues/1377 | 588,045,424 | 1,377 |
[
"WebAssembly",
"wabt"
] | We are researching ways to support custom sections in the text file format (wat) so we can transform it easily to wasm and viceversa.
One of the ideas we came up with is to automatically base64 encode the custom section when decoding from a wasm file, and automatically base64 decode when passing from wat to wasm.
... | Custom sections wasm2wat / wat2wasm | https://api.github.com/repos/WebAssembly/wabt/issues/1376/comments | 14 | 2020-03-25T21:44:38Z | 2023-10-03T13:44:31Z | https://github.com/WebAssembly/wabt/issues/1376 | 588,009,887 | 1,376 |
[
"WebAssembly",
"wabt"
] | There are other TODOs in the source, but most of these should be small.
- [x] Update output from "type" to "func_type" [TODO](https://github.com/WebAssembly/wabt/blob/master/src/binary-reader-logging.cc#L146) [TODO](https://github.com/WebAssembly/wabt/blob/master/src/binary-writer.cc#L888)
- [ ] Rename LoadStoreEx... | Fix Various TODOs | https://api.github.com/repos/WebAssembly/wabt/issues/1375/comments | 6 | 2020-03-25T19:15:25Z | 2023-05-02T09:39:54Z | https://github.com/WebAssembly/wabt/issues/1375 | 587,930,331 | 1,375 |
[
"WebAssembly",
"wabt"
] | See #1275 where these were removed. The upstream spec was changed to use a more generic syntax:
```
(assert_return_canonical_nan (invoke "..."))
```
becomes
```
(assert_return (invoke "...") (nan:canonical))
```
(And similarly for `assert_return_arithmetic_nan` and `nan:arithmetic`).
But in general, ... | Provide backward compatible support for assert_return_arithmetic_nan | https://api.github.com/repos/WebAssembly/wabt/issues/1371/comments | 6 | 2020-03-23T19:16:25Z | 2023-03-15T08:12:25Z | https://github.com/WebAssembly/wabt/issues/1371 | 586,453,036 | 1,371 |
[
"WebAssembly",
"wabt"
] | In https://github.com/WebAssembly/bulk-memory-operations there is a test that checks for a validation error against `data.drop 0`.
https://github.com/WebAssembly/bulk-memory-operations/blob/ffdbb6e357d79818c88c3557cd3325346a057d27/test/core/memory_init.wast#L188
This test fails with a malformed error instead beca... | wast2json not generating wasm with DataCount section when data.drop is used in code | https://api.github.com/repos/WebAssembly/wabt/issues/1368/comments | 0 | 2020-03-22T21:29:31Z | 2020-03-23T18:34:44Z | https://github.com/WebAssembly/wabt/issues/1368 | 585,816,825 | 1,368 |
[
"WebAssembly",
"wabt"
] | ## OS Info
```bash
➜ wabt git:(master) cat /etc/os-release
NAME="Ubuntu"
VERSION="18.04.1 LTS (Bionic Beaver)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 18.04.1 LTS"
VERSION_ID="18.04"
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubu... | build failed: fatal error: wasm.h : No such file or directory | https://api.github.com/repos/WebAssembly/wabt/issues/1367/comments | 2 | 2020-03-22T15:10:12Z | 2020-03-22T15:59:40Z | https://github.com/WebAssembly/wabt/issues/1367 | 585,740,267 | 1,367 |
[
"WebAssembly",
"wabt"
] | See in-progress PR here: https://github.com/WebAssembly/wabt/pull/909.
I was making pretty good progress, but then I stalled out. It would be great if someone else could pick it up, since it's not super easy for me to test on Windows! | Get wasm2c tests running on MSVC/windows | https://api.github.com/repos/WebAssembly/wabt/issues/1366/comments | 1 | 2020-03-20T23:44:42Z | 2022-04-01T06:52:49Z | https://github.com/WebAssembly/wabt/issues/1366 | 585,381,729 | 1,366 |
[
"WebAssembly",
"wabt"
] | I'm getting this test failure when running 1.0.13 test suite on ARM:
```
- test/wasm2c/spec/skip-stack-guard-page.txt
expected error code 0, got 1.
STDERR MISMATCH:
--- expected
+++ actual
@@ -0,0 +1,14 @@
+Traceback (most recent call last):
+ File "/builddir/build/BUILD/wabt-1.0.13/test/run-s... | test/wasm2c/spec/skip-stack-guard-page.txt fails on 32-bit ARM | https://api.github.com/repos/WebAssembly/wabt/issues/1365/comments | 8 | 2020-03-20T22:34:25Z | 2023-01-03T18:36:04Z | https://github.com/WebAssembly/wabt/issues/1365 | 585,360,701 | 1,365 |
[
"WebAssembly",
"wabt"
] | ### Versions
- wabt: 1.0.13 (installed via `brew install wabt`)
- OS: macOS 10.14
### Repro
[foo.wasm.zip](https://github.com/WebAssembly/wabt/files/4357744/foo.wasm.zip)
Unzip above wasm binary and run `wasm-dis foo.wasm -o foo.wat`.
It emits wat file as follows:
```wat
(module
(type $i32_=>_... | wasm-dis emits invalid 'if' instruction in folded form | https://api.github.com/repos/WebAssembly/wabt/issues/1362/comments | 1 | 2020-03-20T02:40:10Z | 2020-03-20T02:50:05Z | https://github.com/WebAssembly/wabt/issues/1362 | 584,808,015 | 1,362 |
[
"WebAssembly",
"wabt"
] | Since https://github.com/WebAssembly/wabt/commit/4c3189d1df4a4062fb2705182a525fd8c23d6af2, I get the following error:
```
[ 1%] Building CXX object CMakeFiles/wabt.dir/src/apply-names.cc.o
In file included from /tmp/wabt/src/apply-names.cc:17:
In file included from /tmp/wabt/src/apply-names.h:20:
In file included... | Compilation error on OpenBSD/clang | https://api.github.com/repos/WebAssembly/wabt/issues/1359/comments | 0 | 2020-03-14T17:16:45Z | 2020-03-15T17:12:05Z | https://github.com/WebAssembly/wabt/issues/1359 | 581,292,338 | 1,359 |
[
"WebAssembly",
"wabt"
] | Attaching example that fails to disassemble with
> 000023c: error: unexpected opcode: 0xfd 0x82 0x1
[decoder_simd.wasm.zip](https://github.com/WebAssembly/wabt/files/4238833/decoder_simd.wasm.zip)
| wasm-objdump: i32x4.max_s et al are not supported | https://api.github.com/repos/WebAssembly/wabt/issues/1343/comments | 2 | 2020-02-22T05:00:19Z | 2020-02-25T06:58:31Z | https://github.com/WebAssembly/wabt/issues/1343 | 569,282,291 | 1,343 |
[
"WebAssembly",
"wabt"
] | LLVM still builds code using the old encoding for `i8x16.shuffle`--`0xfd03`. WABT expects code to have the [new encoding](https://github.com/WebAssembly/simd/blob/master/proposals/simd/BinarySIMD.md)--`0xfdc1`. Over in an [emscripten issue](https://github.com/emscripten-core/emscripten/issues/9281#issuecomment-58933914... | Can't decode LLVM-built i8x16.shuffle | https://api.github.com/repos/WebAssembly/wabt/issues/1339/comments | 3 | 2020-02-21T00:08:51Z | 2020-02-24T20:20:11Z | https://github.com/WebAssembly/wabt/issues/1339 | 568,657,185 | 1,339 |
[
"WebAssembly",
"wabt"
] | ### Steps to Reproduce
```
$ wasm2wat --enable-multi-value --no-check foo.wasm
```
### Test Case
https://github.com/bytecodealliance/wasmparser/files/4171056/foo.wasm.2.gz
### Actual Results
```
0000081: error: invalid call function index: 2097156
```
### Expected Results
(Produced by https://... | wasm2wat fails to disassemble invalid wasm file, even with --no-check | https://api.github.com/repos/WebAssembly/wabt/issues/1331/comments | 2 | 2020-02-07T20:02:17Z | 2020-03-11T17:24:03Z | https://github.com/WebAssembly/wabt/issues/1331 | 561,843,604 | 1,331 |
[
"WebAssembly",
"wabt"
] | When I try to build wabt 1.0.13 from source, the build fails because wasm.h is not present in the source package.
I know that wasm.h is present in binaryen, but I don't understand how
src/interp/interp-wasm-c-api.cc
can be built from source in wabt without wasm.h.
In version 1.0.12 wasm.h was not required ... | wabt fails to build from source because of missing wasm.h | https://api.github.com/repos/WebAssembly/wabt/issues/1315/comments | 17 | 2020-01-23T01:13:45Z | 2021-03-14T17:07:57Z | https://github.com/WebAssembly/wabt/issues/1315 | 553,885,312 | 1,315 |
[
"WebAssembly",
"wabt"
] | Please don't require Git to build wabt. Similar to binaryen
https://github.com/WebAssembly/binaryen/issues/2563
Git is currently required to determine the version string. It would be great if wabt used the same method as binaryen to determine the version string. | Please don't require Git to build wabt | https://api.github.com/repos/WebAssembly/wabt/issues/1314/comments | 0 | 2020-01-23T01:05:14Z | 2020-01-24T01:50:05Z | https://github.com/WebAssembly/wabt/issues/1314 | 553,883,107 | 1,314 |
[
"WebAssembly",
"wabt"
] | With release 1.0.13 the tool wat2wasm.exe with the command line parameter "--enable-reference-types" produce ever a DataCount section with zero entries.
Is this expected? I would expected that an empty section is not written never to reduce size and prevent such problems.
Are there any workarounds with wat2wasm t... | WebAssembly.compile(): unexpected section <DataCount> | https://api.github.com/repos/WebAssembly/wabt/issues/1311/comments | 3 | 2020-01-18T12:12:10Z | 2020-01-21T19:30:14Z | https://github.com/WebAssembly/wabt/issues/1311 | 551,761,325 | 1,311 |
[
"WebAssembly",
"wabt"
] | If i use wasm-decompile the source / math is completely different to wasm2c
and using the math from either does not yeild the correct result compared to the original...
ie from nodejs...
```javascript
var t = [98, 111, 101, 110, 49, 110, 101, 57, 56, 99, 48, 104, 53, 49, 113, 53, 114, 51, 107, 48];
var fs =... | Decompiler doesn't yeild same result | https://api.github.com/repos/WebAssembly/wabt/issues/1307/comments | 1 | 2020-01-15T02:59:49Z | 2020-01-15T04:27:32Z | https://github.com/WebAssembly/wabt/issues/1307 | 549,935,820 | 1,307 |
[
"WebAssembly",
"wabt"
] | We currently have it as the `gh-pages` branch, but it will be easier to update if it was on `master`. See https://github.com/WebAssembly/wabt/pull/1295#discussion_r366575581 | Move documentation to subdirectory of main branch | https://api.github.com/repos/WebAssembly/wabt/issues/1306/comments | 0 | 2020-01-14T22:42:59Z | 2020-03-11T17:27:12Z | https://github.com/WebAssembly/wabt/issues/1306 | 549,861,338 | 1,306 |
[
"WebAssembly",
"wabt"
] | It looks like narrow and widen instructions aren't supported by the disassembler, so getting errors like this:
> 00009c3: error: unexpected opcode: 0xfd 0xca 0x1
[decoder_simd.zip](https://github.com/WebAssembly/wabt/files/4051426/decoder_simd.zip)
| wasm-objdump: Missing support for i16x8.widen_low_i8x16_s et al | https://api.github.com/repos/WebAssembly/wabt/issues/1300/comments | 1 | 2020-01-12T21:06:05Z | 2020-01-14T17:24:33Z | https://github.com/WebAssembly/wabt/issues/1300 | 548,626,995 | 1,300 |
[
"WebAssembly",
"wabt"
] | I'm attempting to perform analysis on this file - http://www.filedropper.com/buildexewasmcode
This file originates from a Unity WebGL Project, this is how they describe this file "build.wasm.code.unityweb file containing the WebAssembly binary."
- more about unity WebGl here https://docs.unity3d.com/Manual/webgl-b... | Problems with wasm binary created with UnityWebGL | https://api.github.com/repos/WebAssembly/wabt/issues/1299/comments | 1 | 2020-01-11T20:44:48Z | 2020-01-11T22:11:30Z | https://github.com/WebAssembly/wabt/issues/1299 | 548,478,157 | 1,299 |
[
"WebAssembly",
"wabt"
] | I am converting some c++ code to wasm with em++ as follows
em++ -o enums.wasm -c -s WASM -s STANDALONE_WASM=1 -std=c++17 -g -O2 enums.cpp
Then I want to produce readable text as follows:
wasm2wat enums.wasm -o enums.wat
Which results in an error:
0000270: error: invalid section code: 12
In the doc th... | wasm2wat produces 'error: invalid section code: 12' | https://api.github.com/repos/WebAssembly/wabt/issues/1292/comments | 4 | 2020-01-09T15:42:07Z | 2020-01-09T18:11:24Z | https://github.com/WebAssembly/wabt/issues/1292 | 547,557,344 | 1,292 |
[
"WebAssembly",
"wabt"
] | Given an input `*.wast` file:
```wat
(module)
(module
(func $f)
(func $g)
(table $t funcref (elem (ref.func $f) (ref.null) (ref.func $g)))
)
(module)
```
Executing:
```sh
$ mkdir tmp
$ wast2json foo.wast -o tmp/foo.json --enable-all
$ ls tmp
foo.0.wasm foo.1.wasm foo.json
```
that... | wast2json drops module with funcref table | https://api.github.com/repos/WebAssembly/wabt/issues/1291/comments | 2 | 2020-01-09T15:13:09Z | 2020-01-10T19:18:21Z | https://github.com/WebAssembly/wabt/issues/1291 | 547,539,112 | 1,291 |
[
"WebAssembly",
"wabt"
] | i'm compiling rust project to wasm with `wasm-pack`, then converting resulting wasm to wat and trying to read it.
currently I can find functions by their original names, but function params and variables lack original names.
so for this rust function
```rust
pub fn add_two(my_param: i32) -> i32 {
let my_... | wasm2wat can't read debug names of params / vars | https://api.github.com/repos/WebAssembly/wabt/issues/1290/comments | 5 | 2020-01-09T04:41:20Z | 2020-01-10T14:14:28Z | https://github.com/WebAssembly/wabt/issues/1290 | 547,244,813 | 1,290 |
[
"WebAssembly",
"wabt"
] | Hi,
I'm using wast2json as part of a test suite for a pet project. when using it with the reference test suite's `elem.wast` (https://github.com/WebAssembly/testsuite/blob/master/elem.wast#L15), the resulting first module is using the new segment flags which AFAIK are part of the bulk memory proposal, which that mea... | wast2json outputs wasm code using segment flags which are not part of the MVP | https://api.github.com/repos/WebAssembly/wabt/issues/1281/comments | 1 | 2020-01-04T17:15:51Z | 2020-01-09T06:10:56Z | https://github.com/WebAssembly/wabt/issues/1281 | 545,308,499 | 1,281 |
[
"WebAssembly",
"wabt"
] | This is a suggestion for a feature request.
## Idea ##
Convert WAT, representation of a Wasm binary, into a language-independent data format so that the information can be transmitted across the web and also parsed (by any language) for inspection.
## Why ##
As far as I can tell, after unsuccessfully attempting... | Dynamic discovery of Wasm functions, params and result. | https://api.github.com/repos/WebAssembly/wabt/issues/1280/comments | 1 | 2020-01-02T23:47:34Z | 2020-01-09T06:10:58Z | https://github.com/WebAssembly/wabt/issues/1280 | 544,795,834 | 1,280 |
[
"WebAssembly",
"wabt"
] | I create a new Wat project in
I edit a wat file with memory.grow and memory.size, such as the one below (just for illustration):
```
(module
(func $add (param $lhs i32) (param $rhs i32) (result i32)
get_local $lhs
get_local $rhs
memory.grow
memory.size
i32.add)
(export "add" (func $... | Getting errors on memory.grow and memory.size on https://webassembly.studio/ | https://api.github.com/repos/WebAssembly/wabt/issues/1274/comments | 1 | 2019-12-21T17:54:09Z | 2020-01-08T23:53:46Z | https://github.com/WebAssembly/wabt/issues/1274 | 541,353,092 | 1,274 |
[
"WebAssembly",
"wabt"
] | Ran into this issue when reviewing some recent additions.
Currently the only documentation I could find was that we specify `BasedOnStyle: Chromium` in `.clang-format`. This implicitly locks down a lot of things which good, more explicit docs would be good.
The specific issue we ran into was the wabt uses a sty... | C++ coding style is not documented | https://api.github.com/repos/WebAssembly/wabt/issues/1273/comments | 5 | 2019-12-19T23:19:02Z | 2020-01-09T00:44:02Z | https://github.com/WebAssembly/wabt/issues/1273 | 540,635,069 | 1,273 |
[
"WebAssembly",
"wabt"
] | Given this input:
```
(module
(func $f)
(global (export "g") anyref (ref.func $f))
)
```
round-tripping this yields:
```
$ wat2wasm foo.wat -o foo.wasm --enable-all
$ wasm2wat foo.wasm --enable-all
foo.wasm:0000017: error: type mismatch at global initializer expression. got void, expected anyref
$... | Anyref global initializer fails in `wasm2wat` | https://api.github.com/repos/WebAssembly/wabt/issues/1270/comments | 1 | 2019-12-18T19:44:39Z | 2020-01-10T19:56:25Z | https://github.com/WebAssembly/wabt/issues/1270 | 539,883,775 | 1,270 |
[
"WebAssembly",
"wabt"
] | Given this `*.wat`:
```wat
(module
(table 1 funcref)
(elem (table 0) (i32.const 0) funcref))
```
this encodes as:
```
$ wat2wasm foo.wat --enable-all -o foo.wasm
$ wasm-objdump -x foo.wasm
foo.wasm: file format wasm 0x1
Section Details:
Table[1]:
- table[0] type=funcref initial=1
Elem[1]:... | Binary encoding for empty funcref segment may use wrong flags? | https://api.github.com/repos/WebAssembly/wabt/issues/1269/comments | 1 | 2019-12-17T21:58:45Z | 2020-01-09T06:13:36Z | https://github.com/WebAssembly/wabt/issues/1269 | 539,332,463 | 1,269 |
[
"WebAssembly",
"wabt"
] | Given a module that looks like:
```wat
(module
(table 1 funcref)
(elem (table 0) (i32.const 0)))
```
this uses the nifty new `(table 0)` syntax to clarify that the `elem` segment is part of a particular table. This `*.wat`, however, is MVP-compatible but ends up being encoded as:
```
$ wat2wasm foo.wa... | Binary encoding of element segment uses non-MVP encoding when it could otherwise do so | https://api.github.com/repos/WebAssembly/wabt/issues/1268/comments | 1 | 2019-12-17T21:55:57Z | 2020-01-09T06:13:15Z | https://github.com/WebAssembly/wabt/issues/1268 | 539,331,314 | 1,268 |
[
"WebAssembly",
"wabt"
] | I wasn't able to find much documentation about libwabt.js, but I was able to piece this together from various sources. Corrections/elaborations are invited.
### Usage ###
Call either `parseWat(filename:string, watSource:string, features: object)` or `readWasm(buffer: Uint8Array, {readDebugNames:true})`.
The `f... | More docs for building/using libwabt? | https://api.github.com/repos/WebAssembly/wabt/issues/1267/comments | 5 | 2019-12-15T17:15:23Z | 2024-03-09T04:53:25Z | https://github.com/WebAssembly/wabt/issues/1267 | 538,079,380 | 1,267 |
[
"WebAssembly",
"wabt"
] | Function inlining can increase performance in x2 for different algorithms. But readability become worsens after that. I suggest to create a some directive for `wat2wasm` preprocessor.
```webassembly
;;@inline
(func $add (param $a f64) (param $b f64) (result f64)
(f64.add (get_local $a) (get_local $b))
)
``` | [wat2wasm] directive @inline for preprocessor | https://api.github.com/repos/WebAssembly/wabt/issues/1260/comments | 3 | 2019-12-09T14:44:32Z | 2020-01-09T01:08:38Z | https://github.com/WebAssembly/wabt/issues/1260 | 534,977,993 | 1,260 |
[
"WebAssembly",
"wabt"
] | A very simple wat file copied from https://github.com/WebAssembly/spec/blob/master/test/core/elem.wast
(module
(table $t 10 funcref)
(func $f)
;; (elem (i32.const 0))
(elem $t (offset (i32.const 0)))
)
The generated wasm file:
00000000 00 61 73 6d 01 00 00 00 01 04 01 60 00 00 03 02 |.asm.......`.... | The latest version of wat2wasm generates malformed wasm file for 'elem' statement | https://api.github.com/repos/WebAssembly/wabt/issues/1259/comments | 1 | 2019-12-09T08:36:08Z | 2020-01-09T06:13:57Z | https://github.com/WebAssembly/wabt/issues/1259 | 534,772,379 | 1,259 |
[
"WebAssembly",
"wabt"
] | Is there a roadmap of typed function references and GC proposal support?
Tools like **wasm-interp** or **wasm2c** would be useful to test compilers while waiting for browser support. | GC proposal | https://api.github.com/repos/WebAssembly/wabt/issues/1257/comments | 2 | 2019-11-30T18:09:38Z | 2020-03-04T03:03:48Z | https://github.com/WebAssembly/wabt/issues/1257 | 530,612,529 | 1,257 |
[
"WebAssembly",
"wabt"
] | Run CI with -Werror (cmake -DWERROR=ON) | https://api.github.com/repos/WebAssembly/wabt/issues/1249/comments | 1 | 2019-11-22T02:31:32Z | 2020-08-19T00:44:53Z | https://github.com/WebAssembly/wabt/issues/1249 | 526,950,650 | 1,249 | |
[
"WebAssembly",
"wabt"
] | Currently we are not catching python3 regressions: https://github.com/WebAssembly/wabt/issues/1180 | Run CI with python3 (as well as python2 for a while) | https://api.github.com/repos/WebAssembly/wabt/issues/1248/comments | 1 | 2019-11-22T02:31:06Z | 2020-01-10T19:19:09Z | https://github.com/WebAssembly/wabt/issues/1248 | 526,950,537 | 1,248 |
[
"WebAssembly",
"wabt"
] | It looks like the test running the array of failed tests contain `Error` class as well as `TestResult`.. perhaps we should embed the `Error` in the `TestResult` on timeout to avoid this discrepancy?
```
./test/run-tests.py test/spec/memory_grow.txt -t0.1
- test/spec/memory_grow.txt
TIMEOUT
STDOUT:
ST... | Crash in test running when a test times out | https://api.github.com/repos/WebAssembly/wabt/issues/1243/comments | 1 | 2019-11-21T20:03:04Z | 2020-03-11T17:28:26Z | https://github.com/WebAssembly/wabt/issues/1243 | 526,812,361 | 1,243 |
[
"WebAssembly",
"wabt"
] | I'm using WAT as a first-class language, and have an issue resolving imports: If one module exports a value, and another module imports that value, there is no (clean) way for the host to resolve the import, unless it knows what the files contain in advance.
When using the JavaScript API (though this seems to apply ... | WAT imports cannot be resolved dynamically. | https://api.github.com/repos/WebAssembly/wabt/issues/1229/comments | 1 | 2019-11-17T22:01:16Z | 2020-03-20T20:37:47Z | https://github.com/WebAssembly/wabt/issues/1229 | 524,054,701 | 1,229 |
[
"WebAssembly",
"wabt"
] | Given this module:
```wat
(module
(func)
(func
ref.func 0
drop))
```
this yields:
```
$ wat2wasm --enable-all foo.wat -o foo.wasm
$ wasm2wat foo.wasm --enable-all
(module
(type (;0;) (func))
(func (;0;) (type 0))
(func (;1;) (type 0)
ref.func
0
drop))
```
A pret... | Formatting of `ref.func` inserts an extra newline by accident | https://api.github.com/repos/WebAssembly/wabt/issues/1228/comments | 0 | 2019-11-15T23:30:14Z | 2019-12-11T23:01:49Z | https://github.com/WebAssembly/wabt/issues/1228 | 523,745,852 | 1,228 |
[
"WebAssembly",
"wabt"
] | Given a module like:
```wat
(module
(func (param v128) (result v128)
local.get 0
local.get 0
v8x16.shuffle 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0))
```
I get:
```
$ wat2wasm foo.wat -o foo.wasm --enable-simd
$ wasm2wat ./foo.wasm --enable-simd
(module
(type (;0;) (func (param v128) (result v... | Formatting of `v8x16.shuffle` has some extraneous whitespace | https://api.github.com/repos/WebAssembly/wabt/issues/1227/comments | 2 | 2019-11-15T23:27:22Z | 2020-03-24T00:32:55Z | https://github.com/WebAssembly/wabt/issues/1227 | 523,745,036 | 1,227 |
[
"WebAssembly",
"wabt"
] | Given a module like so:
```wat
(module
(func $foo)
(func $bar
call $foo)
(start $foo))
```
it generates the following output:
```sh
$ wat2wasm foo.wat -o foo.wasm --debug-names
$ wasm2wat ./foo.wasm
(module
(type (;0;) (func))
(func $foo (type 0))
(func $bar (type 0)
call $foo)... | `wasm2wat` doesn't give the start function a pretty name | https://api.github.com/repos/WebAssembly/wabt/issues/1226/comments | 0 | 2019-11-15T23:22:34Z | 2020-01-09T19:42:50Z | https://github.com/WebAssembly/wabt/issues/1226 | 523,743,329 | 1,226 |
[
"WebAssembly",
"wabt"
] | There are a still a few outstanding issues and we don't yet run the reference-types spec tests. | Finish implementing reference-types and integrate all spec tests | https://api.github.com/repos/WebAssembly/wabt/issues/1223/comments | 1 | 2019-11-15T16:53:53Z | 2019-11-22T08:23:47Z | https://github.com/WebAssembly/wabt/issues/1223 | 523,580,671 | 1,223 |
[
"WebAssembly",
"wabt"
] | Hi,
I believe that `wasm-validate` reports the wrong binary location in its error messages.
## Example
Validating following file generated via `wast2json` from the [spec test i32.wast][1]
```bash
$ xxd test/core/wasm/i32/i32.wast.8.wasm
00000000: 0061 736d 0100 0000 0104 0160 0000 0302 .asm.......`....
000000... | [wasm-validate] Wrong binary location reported in error message | https://api.github.com/repos/WebAssembly/wabt/issues/1217/comments | 4 | 2019-11-10T00:35:11Z | 2021-09-17T12:03:34Z | https://github.com/WebAssembly/wabt/issues/1217 | 520,533,774 | 1,217 |
[
"WebAssembly",
"wabt"
] | Greetings wabt developers and contributors,
We’re reaching out because your project is an important part of the open source ecosystem, and we’d like to invite you to integrate with our [fuzzing](https://www.owasp.org/index.php/Fuzzing) service, [OSS-Fuzz]( https://opensource.googleblog.com/2016/12/announcing-oss-fuz... | Integrating with OSS-Fuzz | https://api.github.com/repos/WebAssembly/wabt/issues/1212/comments | 26 | 2019-11-07T19:47:31Z | 2020-01-09T00:30:40Z | https://github.com/WebAssembly/wabt/issues/1212 | 519,475,023 | 1,212 |
[
"WebAssembly",
"wabt"
] | A discussion about adding sourcemap support came up on twitter. There's an old PR (#432), that could be revived, but we may want to approach this differently now. @dschuff @sbc100 thoughts? | Sourcemap support for wat2wasm? | https://api.github.com/repos/WebAssembly/wabt/issues/1210/comments | 6 | 2019-11-07T14:17:01Z | 2022-03-27T14:33:39Z | https://github.com/WebAssembly/wabt/issues/1210 | 519,293,431 | 1,210 |
[
"WebAssembly",
"wabt"
] | With:
```
$ clang -v
clang version 10.0.0 (https://github.com/llvm/llvm-project/ 64a362e7216a43e3ad44e50a89265e72aeb14294)
Target: x86_64-unknown-linux-gnu
Thread model: posix
```
I'm seeing:
```
test-hexfloat.cc:109:7: warning: implicit conversion from 'unsigned int' to 'float' changes value from 429496... | implicit-int-float-conversion warnings in test-hexfloat.cc | https://api.github.com/repos/WebAssembly/wabt/issues/1200/comments | 0 | 2019-10-25T00:10:48Z | 2020-01-08T19:46:47Z | https://github.com/WebAssembly/wabt/issues/1200 | 512,238,274 | 1,200 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.