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"
] | Hi 👋 and thanks for the super-helpful project!
On my Mac I ca reproduce as follows (in a tmp folder):
```bash
git clone https://github.com/WebAssembly/testsuite.git
wget https://github.com/WebAssembly/wabt/releases/download/1.0.34/wabt-1.0.34-macos-12.tar.gz
./wabt-1.0.34/bin/wast2json ./testsuite/if.wast
``... | `wast2json` fails to parse `if.wast` from latest testsuite | https://api.github.com/repos/WebAssembly/wabt/issues/2347/comments | 4 | 2023-12-04T11:45:29Z | 2023-12-05T18:47:39Z | https://github.com/WebAssembly/wabt/issues/2347 | 2,023,666,826 | 2,347 |
[
"WebAssembly",
"wabt"
] | I have a 16-core 7950X and a 16-core M3 MBP. They both build the Firefox source code in roughly the same amount of time...or would, but for the `wasm2c` invocation takes about 1 minute on the former and over 3 minutes on the latter.
For further discussion see: https://bugzilla.mozilla.org/show_bug.cgi?id=1867594#c6
... | wasm2c is multiple times slower on Apple ARM processors (M3) than x86-64 | https://api.github.com/repos/WebAssembly/wabt/issues/2343/comments | 2 | 2023-12-01T20:17:26Z | 2024-01-25T19:39:23Z | https://github.com/WebAssembly/wabt/issues/2343 | 2,021,527,656 | 2,343 |
[
"WebAssembly",
"wabt"
] | Hi @everyone,
I need assistance with using the "wat2wasm" conversion tool correctly.
- For demonstration, I have chosen the file "left-to-right.wast," available [here](https://github.com/WebAssembly/testsuite/blob/dc27dad3e34e466bdbfea32fe3c73f5e31f88560/left-to-right.wast).
- When using the "wat2wasm" tool, I... | Need Help | wat2wasm: "error: unexpected token" | https://api.github.com/repos/WebAssembly/wabt/issues/2337/comments | 5 | 2023-11-27T12:30:13Z | 2023-11-29T16:21:55Z | https://github.com/WebAssembly/wabt/issues/2337 | 2,012,171,181 | 2,337 |
[
"WebAssembly",
"wabt"
] | I can see that _wat2wasm_ does have the option to enable "gc", but when running the example below (with all features enabled), it fail. The example is from the article: https://v8.dev/blog/wasm-gc-porting
```wat
(module
(type $Node (struct (field $next (ref null $Node)) (field $value (mut i32))))
(global $g... | Unexpected token "null" with WasmGC example | https://api.github.com/repos/WebAssembly/wabt/issues/2333/comments | 1 | 2023-11-20T09:17:52Z | 2023-12-05T01:24:35Z | https://github.com/WebAssembly/wabt/issues/2333 | 2,001,710,359 | 2,333 |
[
"WebAssembly",
"wabt"
] | wasm2c memories currently only take size into account. Splitting into size and capacity would impact threads/shared memory support (since realloc is unsound) but is also relevant for big-endian (both guard pages and shared memory). cc @shravanrn
(This also lets the runtime use more efficient memory growth strategie... | wasm2c: Split size and capacity | https://api.github.com/repos/WebAssembly/wabt/issues/2329/comments | 0 | 2023-11-15T10:08:39Z | 2023-11-15T10:09:33Z | https://github.com/WebAssembly/wabt/issues/2329 | 1,994,455,065 | 2,329 |
[
"WebAssembly",
"wabt"
] | Instead of merely emitting data segments as array initializers, it would be neat if we could (optionally) use `#embed` too.
Too bad `offset(...)` isn't standard so we'll need to emit separate files for each data segment. | wasm2c: Optionally support #embed | https://api.github.com/repos/WebAssembly/wabt/issues/2325/comments | 7 | 2023-11-11T12:36:28Z | 2023-11-12T07:06:48Z | https://github.com/WebAssembly/wabt/issues/2325 | 1,988,929,525 | 2,325 |
[
"WebAssembly",
"wabt"
] | wasm2c.exe on Windows 10, ran through MSys2, does nothing at all since wabt 1.0.33. Nothing in stdout, nothing in output files, it appears to just not do anything. Only wabt 1.0.32 works correctly.
The following are tested using the last 3 releases named `wabt-1.0.3x-windows.tar.gz`
```
user@DESKTOP-AP5KGUV ~/ho... | wasm2c does nothing at all | https://api.github.com/repos/WebAssembly/wabt/issues/2323/comments | 4 | 2023-11-08T11:05:54Z | 2023-12-05T18:37:14Z | https://github.com/WebAssembly/wabt/issues/2323 | 1,983,344,340 | 2,323 |
[
"WebAssembly",
"wabt"
] | ## Environments
**OS** : Ubuntu 18.04 5.4.0-150-generic
**Commit** : e97d53c5fcbb604fc36432df4fc117d13558d7fd
**Version** : 1.0.34
## Vulnerability Description
**Affected Tool** : wasm-decompile
**Affected Version** : <= 1.0.34
**Impact** : Denial of Service
* The assertion 'false' in /src/decompiler.cc... | wasm-decompile: Assertion `false' failed. | https://api.github.com/repos/WebAssembly/wabt/issues/2322/comments | 1 | 2023-11-06T05:27:20Z | 2023-11-06T05:44:07Z | https://github.com/WebAssembly/wabt/issues/2322 | 1,978,321,551 | 2,322 |
[
"WebAssembly",
"wabt"
] | I noticed that wasm-objdump can dump all functions and symbols
but it does it weirdly
it doesen't quite go functions (then their data) it seems to switch between all the diffrent data assocated whether being size, where it is pulled from etc | [Feature/Binary Request] List Exported functions only | https://api.github.com/repos/WebAssembly/wabt/issues/2320/comments | 11 | 2023-11-02T19:23:17Z | 2023-11-04T06:03:57Z | https://github.com/WebAssembly/wabt/issues/2320 | 1,974,904,203 | 2,320 |
[
"WebAssembly",
"wabt"
] | ## Environments
**OS** : Ubuntu 18.04 5.4.0-150-generic
**Commit** : e97d53c5fcbb604fc36432df4fc117d13558d7fd
**Version** : 1.0.34
## Vulnerability Description
**Affected Tool** : wasm2c
**Affected Version** : <= 1.0.34
**Impact** : Denial of Service
* The 'std::out_of_range' error in wabt 1.0.34 can ca... | Invalid basic_string_view::substr:__pos() number cause DoS | https://api.github.com/repos/WebAssembly/wabt/issues/2318/comments | 2 | 2023-10-29T14:22:47Z | 2023-11-05T17:19:28Z | https://github.com/WebAssembly/wabt/issues/2318 | 1,967,011,228 | 2,318 |
[
"WebAssembly",
"wabt"
] | ## Environments
**OS** : Ubuntu 18.04 5.4.0-150-generic
**Commit** : e97d53c5fcbb604fc36432df4fc117d13558d7fd
**Version** : 1.0.34
## Vulnerability Description
**Affected Tool** : wasm-decompile
**Affected Version** : <= 1.0.34
**Impact** : Denial of Service
* The assertion 'exp_stack.size() >= nargs' f... | wasm-decompile: Assertion `exp_stack.size() >= nagrs' failure cause DoS | https://api.github.com/repos/WebAssembly/wabt/issues/2317/comments | 0 | 2023-10-29T14:09:33Z | 2023-10-29T14:09:33Z | https://github.com/WebAssembly/wabt/issues/2317 | 1,967,006,559 | 2,317 |
[
"WebAssembly",
"wabt"
] | ## Environments
**OS** : Ubuntu 18.04 5.4.0-150-generic
**Commit** : e97d53c5fcbb604fc36432df4fc117d13558d7fd
**Version** : 1.0.34
## Vulnerability Description
**Affected Tool** : wasm-decompile
**Affected Version** : <= 1.0.34
**Impact** : Denial of Service
* The assertion '!empty()' fail in /include/w... | wasm-decompile: Assertion `!empty()' failure cause DoS | https://api.github.com/repos/WebAssembly/wabt/issues/2316/comments | 0 | 2023-10-29T14:03:47Z | 2023-10-29T14:03:47Z | https://github.com/WebAssembly/wabt/issues/2316 | 1,967,004,525 | 2,316 |
[
"WebAssembly",
"wabt"
] | ## Environments
**OS** : Ubuntu 18.04 5.4.0-150-generic
**Commit** : e97d53c5fcbb604fc36432df4fc117d13558d7fd
**Version** : 1.0.34
## Vulnerability Description
**Affected Tool** : wasm-interp
**Affected Version** : <= 1.0.34
**Impact** : Denial of Service
* The ReadBinaryInterp function in src/interp/bina... | Memory allocation error in ReadBinaryInterp() cause DoS | https://api.github.com/repos/WebAssembly/wabt/issues/2315/comments | 0 | 2023-10-29T13:49:22Z | 2023-10-29T13:49:22Z | https://github.com/WebAssembly/wabt/issues/2315 | 1,966,999,344 | 2,315 |
[
"WebAssembly",
"wabt"
] | The wasm-stats tool outputs opcode counts for a wasm file. It would be really helpful if it could also build a markov chain from the opcodes in a wasm file, or the probability that a given opcode is followed by any other opcodes. As we now know, inlining isn't actually helpful with wasm, and such markov chains would he... | wasm-stats: support markov chain style listings | https://api.github.com/repos/WebAssembly/wabt/issues/2312/comments | 7 | 2023-10-08T13:16:52Z | 2023-10-10T06:56:17Z | https://github.com/WebAssembly/wabt/issues/2312 | 1,931,802,335 | 2,312 |
[
"WebAssembly",
"wabt"
] | ### Environment
```shell
OS : Linux 5.10.16.3-microsoft-standard-WSL2 #1 SMP Fri Apr 2 22:23:49 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
Commit : 0e78c24fd231d5ee67ccd271bfa317faa963281c
Version : 1.0.33 (git~1.0.33-35-gdddc03d3)
Clang Verison : 12.0.1
Build : mkdir... | Out-of-Bound Memory Write in DataSegment::Drop() | https://api.github.com/repos/WebAssembly/wabt/issues/2311/comments | 0 | 2023-10-08T07:46:31Z | 2023-10-08T18:41:21Z | https://github.com/WebAssembly/wabt/issues/2311 | 1,931,692,043 | 2,311 |
[
"WebAssembly",
"wabt"
] | ### Environment
```shell
OS : Linux 5.10.16.3-microsoft-standard-WSL2 #1 SMP Fri Apr 2 22:23:49 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
Commit : 0e78c24fd231d5ee67ccd271bfa317faa963281c
Version : 1.0.33 (git~1.0.33-35-gdddc03d3)
Clang Verison : 12.0.1
Build : mkdir... | Out-of-Bound Memory Read in DataSegment::IsValidRange() | https://api.github.com/repos/WebAssembly/wabt/issues/2310/comments | 0 | 2023-10-08T07:32:47Z | 2023-10-08T18:41:08Z | https://github.com/WebAssembly/wabt/issues/2310 | 1,931,687,191 | 2,310 |
[
"WebAssembly",
"wabt"
] | I am trying to understand how memory is shared between the host and a WebAssembly module (generated using `wasm2c` from an object file generated with `emcc`).
Consider the following very simple example:
```c
int foo(char *buff) {
return buff[0];
}
```
This is compiled using `emcc` and then `wasm2c` and `... | Sharing memory between the host and a WebAssembly module | https://api.github.com/repos/WebAssembly/wabt/issues/2307/comments | 7 | 2023-09-27T13:51:22Z | 2023-10-31T17:13:22Z | https://github.com/WebAssembly/wabt/issues/2307 | 1,915,640,569 | 2,307 |
[
"WebAssembly",
"wabt"
] | Hello there, the following code snippet is the sample webassembly module (in textual format) I extracted from [here](https://github.com/WebAssembly/spec/blob/main/test/core/bulk.wast#L154):
```wasm
(module
(type (;0;) (func))
(type (;1;) (func (param i32)))
(func (;0;) (type 0)
data.drop 0)
(func (... | wasm-interp errors on seemingly semantically-correct wasm module | https://api.github.com/repos/WebAssembly/wabt/issues/2306/comments | 1 | 2023-09-27T07:21:49Z | 2023-09-27T09:01:07Z | https://github.com/WebAssembly/wabt/issues/2306 | 1,914,865,352 | 2,306 |
[
"WebAssembly",
"wabt"
] | wasm-decompile crashes when trying to process [this WAT file](https://github.com/WebAssembly/wabt/files/12731218/test.zip). Interestingly enough, it works after being processed with wasm-opt.
The full text of the error is:
```
wabt-main/include/wabt/ir.h:62: const string& wabt::Var::name() const: Assertion `is... | wasm-decompile: Assertion `is_name()' failed. | https://api.github.com/repos/WebAssembly/wabt/issues/2304/comments | 1 | 2023-09-26T19:40:55Z | 2023-10-05T19:44:03Z | https://github.com/WebAssembly/wabt/issues/2304 | 1,914,182,850 | 2,304 |
[
"WebAssembly",
"wabt"
] | Just experienced an error when trying to run one of the tools on Ubuntu focal / Mint 20.3 (Una). Is it supported?
```
$ wasm2wat plugin.wasm
wasm2wat: /lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.29' not found (required by wasm2wat)
wasm2wat: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.33' not f... | Can't run on Ubuntu focal | https://api.github.com/repos/WebAssembly/wabt/issues/2303/comments | 7 | 2023-09-24T20:54:59Z | 2023-09-25T22:29:15Z | https://github.com/WebAssembly/wabt/issues/2303 | 1,910,376,169 | 2,303 |
[
"WebAssembly",
"wabt"
] | This is an extension of #2301. However, this one is a bit harder - mandoc doesn't appear to have reproducible output, particularly around dates. Anyway, the relevant script is `scripts/generate-html-docs.sh` (which should really be `.bash` but anyway). | Tech debt: keep mandoc html up to date | https://api.github.com/repos/WebAssembly/wabt/issues/2302/comments | 0 | 2023-09-19T22:57:49Z | 2023-09-19T22:59:21Z | https://github.com/WebAssembly/wabt/issues/2302 | 1,903,833,125 | 2,302 |
[
"WebAssembly",
"wabt"
] | There is a script, `scripts/help2man.lua` which can be used to generate manpages from `$wabt_tool --help` output. It could be used in CI to fail if man pages are outdated. | Tech debt: keep man pages up to date | https://api.github.com/repos/WebAssembly/wabt/issues/2301/comments | 0 | 2023-09-19T22:53:00Z | 2023-09-19T22:53:00Z | https://github.com/WebAssembly/wabt/issues/2301 | 1,903,829,731 | 2,301 |
[
"WebAssembly",
"wabt"
] | Currently, wabt has opcodecnt, used to output opcode counts. We would kinda like to see a more general tool to output (and in some sense, visualize) various stats for a given wasm file.
Function/global/import/export counts, opcodes per function, local count (okay it's currently possible to find the max locals using ... | Proposal: stats | https://api.github.com/repos/WebAssembly/wabt/issues/2295/comments | 3 | 2023-09-13T23:44:15Z | 2023-10-08T13:07:48Z | https://github.com/WebAssembly/wabt/issues/2295 | 1,895,404,206 | 2,295 |
[
"WebAssembly",
"wabt"
] | Hey, it's Pedro (see #2245) and I'm back with a new security suggestion!
When developing with CI workflows, it's common to version-pin dependencies (i.e. `actions/checkout@v3`). However, version tags are mutable, so a malicious attacker could overwrite a version tag to point to a malicious or vulnerable commit inste... | Hash-pin workflow GitHub Actions | https://api.github.com/repos/WebAssembly/wabt/issues/2290/comments | 1 | 2023-09-06T13:47:06Z | 2023-09-15T03:16:56Z | https://github.com/WebAssembly/wabt/issues/2290 | 1,884,057,721 | 2,290 |
[
"WebAssembly",
"wabt"
] | I have the following C file, which I have compiled into a `.wasm` module, and then translated to C using `wasm2c`:
```c
#include <stdio.h>
#include <unistd.h>
#include <emscripten.h>
int EMSCRIPTEN_KEEPALIVE unsafe_printf() {
printf("Hello World\n");
return 0;
}
int EMSCRIPTEN_KEEPALIVE unsafe_unlink... | `w2c_env` and `w2c_wasi`: what are they? | https://api.github.com/repos/WebAssembly/wabt/issues/2289/comments | 6 | 2023-08-31T11:54:53Z | 2023-09-06T22:32:27Z | https://github.com/WebAssembly/wabt/issues/2289 | 1,875,378,445 | 2,289 |
[
"WebAssembly",
"wabt"
] | Say we have the file repro.wat with an $invalid function, which doesn't match it's return signature, and a following valid function
with a select instruction:
```
(module
(func $invalid (result i32))
(func $normal (local i32)
i32.const 1
i32.const 2
i32.const 3
select
local.set 0
)
)
```
Trying to build ... | `wasm-validate` gives false positive errors that occur after a true positive. | https://api.github.com/repos/WebAssembly/wabt/issues/2283/comments | 1 | 2023-08-15T03:39:58Z | 2023-08-23T20:49:42Z | https://github.com/WebAssembly/wabt/issues/2283 | 1,850,860,565 | 2,283 |
[
"WebAssembly",
"wabt"
] | I'm encountering an error when trying to convert my wasm file to a wat file using `wasm2wat`. The error is `0003778: error: unexpected opcode: 0xfe 0x25`. I am able to run other tools such as `wasm-decompile` and `wasm-objdump` on the same wasm file. It appears that the opcode means `i32.atomic.rmw.sub` as far as I can... | wasm2wat : Unexpected opcode 0xfe 0x25 | https://api.github.com/repos/WebAssembly/wabt/issues/2281/comments | 2 | 2023-08-10T20:58:33Z | 2023-08-11T13:48:44Z | https://github.com/WebAssembly/wabt/issues/2281 | 1,845,892,592 | 2,281 |
[
"WebAssembly",
"wabt"
] | currently the target `libwabtjs` will export APIs:
```
validate(): void;
resolveNames(): void;
generateNames(): void;
applyNames(): void;
toText(options: ToTextOptions): string;
toBinary(options: ToBinaryOptions): ToBinaryResult;
destroy(): void;
```
is it possible to export the objdump API for ... | Shall the objdump API be included in libwabtjs target | https://api.github.com/repos/WebAssembly/wabt/issues/2279/comments | 0 | 2023-08-03T09:44:29Z | 2023-08-03T09:44:29Z | https://github.com/WebAssembly/wabt/issues/2279 | 1,834,685,260 | 2,279 |
[
"WebAssembly",
"wabt"
] | ## version
```shell
$ git log
commit e37de9dedfc7037cea09ca3c75fd5a544d68cb2a (HEAD -> main, origin/main, origin/HEAD)
Author: Shravan Narayan <shravanrn@gmail.com>
Date: Tue Jun 20 00:06:25 2023 -0400
C++20 compatibility fixes
```
## Env
```shell
host : Linux user 5.19.0-50-generic #50-Ubuntu SM... | huge memory alloc causes SIGABORT signal at reserve function in binary-reader-interp.cc:761 | https://api.github.com/repos/WebAssembly/wabt/issues/2277/comments | 6 | 2023-07-31T08:05:24Z | 2023-08-01T00:43:22Z | https://github.com/WebAssembly/wabt/issues/2277 | 1,828,635,108 | 2,277 |
[
"WebAssembly",
"wabt"
] | wat-desugar (1.0.33) seems to have an overflow issue for the `typeidx` of the `call_indirect` instruction.
e.g.:
This module (located [here](https://github.com/WebAssembly/spec/blob/master/test/core/ref_func.wast)):
``` wat
(module
(func $f (import "M" "f") (param i32) (result i32))
(func $g (param $x i32) ... | desugar: overflow issue for typeidx of call_indirect instruction | https://api.github.com/repos/WebAssembly/wabt/issues/2270/comments | 5 | 2023-07-18T09:34:03Z | 2023-08-01T16:35:20Z | https://github.com/WebAssembly/wabt/issues/2270 | 1,809,550,104 | 2,270 |
[
"WebAssembly",
"wabt"
] | thx | Where I can find binary .exe files? | https://api.github.com/repos/WebAssembly/wabt/issues/2269/comments | 1 | 2023-07-14T13:41:20Z | 2023-07-25T10:08:48Z | https://github.com/WebAssembly/wabt/issues/2269 | 1,804,907,978 | 2,269 |
[
"WebAssembly",
"wabt"
] | When compiling Firefox (which uses wasm2c) for MIPS with clang, the following error happens:
```
rlbox.wasm.c:142:1: error: couldn't allocate input reg for constraint 'r'
DEFINE_LOAD(f32_load, f32, f32, f32)
^
rlbox.wasm.c:128:14: note: expanded from macro 'DEFINE_LOAD'
wasm_asm("" ::"r"(result)); ... | error: couldn't allocate input reg for constraint 'r' on MIPS with clang when compiling wasm2c-generated source | https://api.github.com/repos/WebAssembly/wabt/issues/2266/comments | 10 | 2023-06-30T22:10:20Z | 2023-07-30T19:18:51Z | https://github.com/WebAssembly/wabt/issues/2266 | 1,783,211,051 | 2,266 |
[
"WebAssembly",
"wabt"
] | The module below has two function types declared, `0: () -> ()` and `1: (i32) -> ()`. It also has a single function defined with the second function type i.e. `(i32) -> ()`. That function has a single local defined. Since it has a parameter, my understanding is that the local should have the index 1 in the "Code Disass... | wasm-objdump has incorrect local numbering | https://api.github.com/repos/WebAssembly/wabt/issues/2264/comments | 2 | 2023-06-27T18:56:23Z | 2023-06-27T21:26:21Z | https://github.com/WebAssembly/wabt/issues/2264 | 1,777,572,674 | 2,264 |
[
"WebAssembly",
"wabt"
] | I noticed that the macos archive name in the release is inconsistent vs ubuntu/windows. It has the version name, `-12` while the others don't. This is because the name is computed by stripping out the GHA runner name of `-latest`, but for macos the runner is not `-latest`
https://github.com/WebAssembly/wabt/blob/mai... | Inconsistent archive name for macos | https://api.github.com/repos/WebAssembly/wabt/issues/2259/comments | 3 | 2023-06-12T05:26:26Z | 2024-05-15T01:39:26Z | https://github.com/WebAssembly/wabt/issues/2259 | 1,751,922,281 | 2,259 |
[
"WebAssembly",
"wabt"
] | @keithw @sbc100 I've been looking at finishing the wait/notify part of the thread atomics proposal (https://github.com/WebAssembly/threads/blob/main/proposals/threads/Overview.md) and after going through a few different implementations, I have come to the conclusion that we would definitely need a map and list data str... | wasm2c: we need to pick standard C data structure implementations to finish thread proposal | https://api.github.com/repos/WebAssembly/wabt/issues/2258/comments | 10 | 2023-06-09T07:30:31Z | 2023-06-17T11:10:33Z | https://github.com/WebAssembly/wabt/issues/2258 | 1,749,299,094 | 2,258 |
[
"WebAssembly",
"wabt"
] | WastParser seems to:
- allow `(module binary "...")` in `ParseModule` (even though this is not valid syntax for the Wasm text format; it's only valid for scripts), and
- forbid `(module quote "...")`in `ParseScript`, even though this is a valid script command. (It does allow `(module quote)` when inside `(assert_ma... | WastParser handling of `(module binary)` and `(module quote)` | https://api.github.com/repos/WebAssembly/wabt/issues/2249/comments | 1 | 2023-06-07T17:27:28Z | 2023-12-05T08:07:52Z | https://github.com/WebAssembly/wabt/issues/2249 | 1,746,368,256 | 2,249 |
[
"WebAssembly",
"wabt"
] | if my reading of the spec is correct, an empty wast file is valid.
https://github.com/WebAssembly/spec/blob/main/interpreter/README.md#scripts
an example of such a file:
https://github.com/WebAssembly/multi-memory/blob/4f6b8f53ec11e59f5e38033db4199db18df83706/test/core/multi-memory/memory_copy1.wast#L1
how othe... | wast2json should not complain on an empty wast file | https://api.github.com/repos/WebAssembly/wabt/issues/2246/comments | 1 | 2023-06-07T02:15:31Z | 2023-06-07T20:25:54Z | https://github.com/WebAssembly/wabt/issues/2246 | 1,744,909,556 | 2,246 |
[
"WebAssembly",
"wabt"
] | A security policy (SECURITY.md) explains how the project wishes to receive and handle responsible disclosure of potential vulnerabilities. [GitHub recommends](https://docs.github.com/en/code-security/getting-started/securing-your-repository#setting-a-security-policy) that projects have one.
The security policy can b... | Add a security policy | https://api.github.com/repos/WebAssembly/wabt/issues/2244/comments | 0 | 2023-06-06T20:35:20Z | 2023-08-30T23:08:49Z | https://github.com/WebAssembly/wabt/issues/2244 | 1,744,560,641 | 2,244 |
[
"WebAssembly",
"wabt"
] | This is a silly request but it'd be neat if CI simply randomized LC_ALL.
Yeah it'd mean failure is probabilistic instead of guaranteed, but it'd help expand the test surface. | Randomize LC_ALL in CI? | https://api.github.com/repos/WebAssembly/wabt/issues/2243/comments | 7 | 2023-06-01T21:28:04Z | 2023-08-30T22:45:05Z | https://github.com/WebAssembly/wabt/issues/2243 | 1,737,121,720 | 2,243 |
[
"WebAssembly",
"wabt"
] | wasm-interp crashes with no error message when the wrong number of arguments is given.
For example, when running the identity function:
```wasm
(module
(func (export "id") (param i32) (result i32) (local.get 0))
)
```
```
% wasm-interp identity.wasm --run-export=id
[1] 102759 segmentation fault (cor... | wasm-interp crashes when wrong number of arguments passed | https://api.github.com/repos/WebAssembly/wabt/issues/2242/comments | 5 | 2023-05-29T15:54:24Z | 2023-06-09T18:26:37Z | https://github.com/WebAssembly/wabt/issues/2242 | 1,730,973,298 | 2,242 |
[
"WebAssembly",
"wabt"
] | The following wat program works fine in wat2wasm without function references enabled:
```
(module
(func $example (export "example") (result funcref)
ref.func $example))
```
However, enabling the "function references" feature causes the following error:
```
Error: validate failed:
test.wast:3:5: error: ... | Incorrect type for ref.func when function references are enabled | https://api.github.com/repos/WebAssembly/wabt/issues/2241/comments | 1 | 2023-05-28T19:28:30Z | 2023-05-29T22:52:33Z | https://github.com/WebAssembly/wabt/issues/2241 | 1,729,631,247 | 2,241 |
[
"WebAssembly",
"wabt"
] | When running the test suite of wabt-1.0.33 on aarch64 on Fedora 38, I get this (new) test failure:
```
- test/wasm2c/spec/simd_address.txt
expected error code 0, got 1.
STDERR MISMATCH:
--- expected
+++ actual
@@ -0,0 +1,11 @@
+Traceback (most recent call last):
+ File "/builddir/build/BUILD/wab... | wasm2c/spec/simd_address.txt fails on non-x86 | https://api.github.com/repos/WebAssembly/wabt/issues/2240/comments | 5 | 2023-05-25T19:58:59Z | 2023-05-26T09:54:17Z | https://github.com/WebAssembly/wabt/issues/2240 | 1,726,412,675 | 2,240 |
[
"WebAssembly",
"wabt"
] | In some cases, WastParser rejects constructs that use disabled features (e.g. multi-memory, exceptions) and in some cases it appears to allow them (e.g. extended-const, memory64) even if disabled. (As seen in https://github.com/WebAssembly/wabt/pull/2234 where the lack of `--enable-extended-const` didn't affect `wast2j... | Enforce disabled features in WastParser for extended-const and memory64? | https://api.github.com/repos/WebAssembly/wabt/issues/2235/comments | 1 | 2023-05-11T20:50:28Z | 2023-05-11T21:14:13Z | https://github.com/WebAssembly/wabt/issues/2235 | 1,706,536,550 | 2,235 |
[
"WebAssembly",
"wabt"
] | simd-everywhere has just merged fixes to pass the Wasm testsuite (https://github.com/simd-everywhere/simde/pull/1010), so I think we're close to being able to close this out, cut a release, and check the box on webassembly.org. This will also be the first time in a while that wasm2c is passing 100% of the current Wasm ... | wasm2c SIMD final approach checklist | https://api.github.com/repos/WebAssembly/wabt/issues/2224/comments | 6 | 2023-05-03T22:38:22Z | 2023-07-12T19:29:35Z | https://github.com/WebAssembly/wabt/issues/2224 | 1,694,942,085 | 2,224 |
[
"WebAssembly",
"wabt"
] | #2219 | Validator doesn't quite pass all the spec tests | https://api.github.com/repos/WebAssembly/wabt/issues/2220/comments | 0 | 2023-04-27T09:23:42Z | 2023-04-27T16:28:29Z | https://github.com/WebAssembly/wabt/issues/2220 | 1,686,465,971 | 2,220 |
[
"WebAssembly",
"wabt"
] | same as #2210 but for OpenBSD, cf https://bugzilla.mozilla.org/show_bug.cgi?id=1830036 for the context. | [wasm2c] alloca.h on OpenBSD | https://api.github.com/repos/WebAssembly/wabt/issues/2216/comments | 1 | 2023-04-26T11:15:54Z | 2023-04-26T15:06:50Z | https://github.com/WebAssembly/wabt/issues/2216 | 1,684,820,073 | 2,216 |
[
"WebAssembly",
"wabt"
] | Does it... make any sense to have source maps for wasm2c? | Source maps for wasm2c? | https://api.github.com/repos/WebAssembly/wabt/issues/2215/comments | 5 | 2023-04-25T18:01:21Z | 2023-06-15T13:40:56Z | https://github.com/WebAssembly/wabt/issues/2215 | 1,683,610,559 | 2,215 |
[
"WebAssembly",
"wabt"
] | Sorry if this has been answered elsewhere. I am building directly with CMake and curious about targets in provided Makefile vs the ones generated by CMake, in particular `test-everything` (Makefile) vs `check` (CMake) and `update-gperf` (Makefile only).
Readme doesn't seem to recommend using `check`, though it does ... | [Question] CMake-generated targets vs top-level makefile | https://api.github.com/repos/WebAssembly/wabt/issues/2211/comments | 1 | 2023-04-21T20:51:58Z | 2023-04-22T04:55:01Z | https://github.com/WebAssembly/wabt/issues/2211 | 1,679,083,156 | 2,211 |
[
"WebAssembly",
"wabt"
] | When I try to build on FreeBSD wasm2c tests fail due to lack of `alloca.h` headers (using wasm2c should be problematic because of that). I'm not sure if this happens on other platforms. There are a few potential ways to fix it, for example include `stdlib.h` instead or make the include conditional, either via a preproc... | [wasm2c] alloca.h | https://api.github.com/repos/WebAssembly/wabt/issues/2210/comments | 3 | 2023-04-21T20:43:07Z | 2023-04-22T07:28:25Z | https://github.com/WebAssembly/wabt/issues/2210 | 1,679,068,888 | 2,210 |
[
"WebAssembly",
"wabt"
] | Executing the sequence `wasm_rt_init(); ...; wasm_rt_free();` from `wasm-rt-impl` _twice_ triggers a double free.
This can be reproduced by just duplicating the code of the main function in example `rot13`.
To my understanding the reason is that
1. the first `wasm_rt_free` doesn't reset `g_signal_handler_instal... | wasm2c double free | https://api.github.com/repos/WebAssembly/wabt/issues/2206/comments | 2 | 2023-04-21T01:34:17Z | 2023-04-21T16:58:31Z | https://github.com/WebAssembly/wabt/issues/2206 | 1,677,628,988 | 2,206 |
[
"WebAssembly",
"wabt"
] | ```wast
(func (export "break-try")
(try (do (br 0)) (delegate 0))
)
``` | wasm2c exception handling is more broken than we thought | https://api.github.com/repos/WebAssembly/wabt/issues/2205/comments | 0 | 2023-04-21T00:59:23Z | 2023-05-08T20:49:43Z | https://github.com/WebAssembly/wabt/issues/2205 | 1,677,604,976 | 2,205 |
[
"WebAssembly",
"wabt"
] | ```
;;; TOOL: run-spec-wasm2c
;;; ARGS*: --enable-exceptions
(module
(tag $e0)
(func $throw (throw $e0))
(func (export "break-throw") (result i32)
(try $outer (result i32)
(do
(try (result i32)
(do
(block $a
(try (do (br $a)) (delegate $outer))
... | wasm2c exception handling is broken | https://api.github.com/repos/WebAssembly/wabt/issues/2203/comments | 3 | 2023-04-20T18:02:01Z | 2023-04-21T07:12:12Z | https://github.com/WebAssembly/wabt/issues/2203 | 1,677,180,574 | 2,203 |
[
"WebAssembly",
"wabt"
] | As far as I can tell from the webassembly spec, it should be valid to use the `global.get` instruction in an element segment.
However I am unable to use `wat2wasm` on this module
```wat
(module
(import "m" "f" (global funcref))
(table 0 10 funcref)
(elem 0 (offset (i32.const 0)) funcref (global.get 0)))... | Is `global.get` allowed in element segments? | https://api.github.com/repos/WebAssembly/wabt/issues/2201/comments | 2 | 2023-04-16T20:18:20Z | 2023-09-06T22:54:14Z | https://github.com/WebAssembly/wabt/issues/2201 | 1,670,120,538 | 2,201 |
[
"WebAssembly",
"wabt"
] | I read the instructions in the root README.md file. I chose to do "Building using the top-level Makefile (Linux and macOS)". It complained about the fact that I don't have clang. So I installed it. Then I tried "make" again and it complained about not being able to find "lstdc++" (which I take to mean that the library ... | Docfix: clang issues | https://api.github.com/repos/WebAssembly/wabt/issues/2200/comments | 9 | 2023-04-16T17:15:51Z | 2023-07-31T00:04:10Z | https://github.com/WebAssembly/wabt/issues/2200 | 1,670,051,842 | 2,200 |
[
"WebAssembly",
"wabt"
] | ### Describe the bug
Certain wasm binary causes `wasm2wat`, `wasm2c`, `wasm-decompile`, and `wasm-validate` to crash.
`--version` (for all of them): 1.0.32 (git~1.0.32-57-gad5f1385)
_________________
### Steps to reproduce
The following `wasm` module causes a crash:
[crash.wasm.txt](https://github.com/W... | Certain wasm binary causes `wasm2wat`, `wasm2c`, `wasm-decompile`, and `wasm-validate` to crash. | https://api.github.com/repos/WebAssembly/wabt/issues/2199/comments | 1 | 2023-04-14T07:36:31Z | 2023-05-10T00:46:32Z | https://github.com/WebAssembly/wabt/issues/2199 | 1,667,696,676 | 2,199 |
[
"WebAssembly",
"wabt"
] | Per discussion in #2194
@sbc100 @keith We can definitely write a custom test for this, but would you have thoughts on the best way to add this to the existing harness. The test probably has to look something like this.
```
**Wasm module**
memory size = 1
func foo that accesses memory index 2
**Compilation*... | wasm2c: custom trap handler function needs testing | https://api.github.com/repos/WebAssembly/wabt/issues/2195/comments | 0 | 2023-04-10T17:33:36Z | 2023-04-11T03:30:52Z | https://github.com/WebAssembly/wabt/issues/2195 | 1,661,105,435 | 2,195 |
[
"WebAssembly",
"wabt"
] | In file `wabt/src/leb128.cc`, function `ReadU64Leb128`:
This snippet is incorrect. It appears to have been copied from `ReadU32Leb128`:
```
else if (p + 9 < end && (p[9] & 0x80) == 0) {
// The top bits set represent values > 32 bits.
if (p[9] & 0xf0) {
return 0;
}
*out_value = LEB128_10(uint64_t);... | Copy/paste bug in ReadU64LEB128 | https://api.github.com/repos/WebAssembly/wabt/issues/2192/comments | 2 | 2023-04-08T10:17:35Z | 2023-06-09T19:07:11Z | https://github.com/WebAssembly/wabt/issues/2192 | 1,659,477,193 | 2,192 |
[
"WebAssembly",
"wabt"
] | Trying to get #2046 closed off (use of globals preventing the wasm2c runtime from being thread-safe).
It looks like the only remaining blocker is the `static char* g_alt_stack` variable, which currently gets malloc'ed once per process via `wasm_rt_init()` which calls `os_install_signal_handler()`.
The challenge i... | wasm2c runtime: add per-thread init/free, and make wasm_rt_init/free return and take a `void*`? | https://api.github.com/repos/WebAssembly/wabt/issues/2189/comments | 3 | 2023-04-06T18:40:21Z | 2023-12-04T02:23:04Z | https://github.com/WebAssembly/wabt/issues/2189 | 1,657,882,802 | 2,189 |
[
"WebAssembly",
"wabt"
] | I don't know to what degree that matters, but #1968 disabled building on latest LTS Ubuntu (22.04), which only has CMake 3.14 at the moment. Ubuntu tends to lag behind Debian.
| Ubuntu 22.04 doesn't have CMake 3.16 | https://api.github.com/repos/WebAssembly/wabt/issues/2187/comments | 4 | 2023-04-06T17:17:06Z | 2023-04-06T18:42:12Z | https://github.com/WebAssembly/wabt/issues/2187 | 1,657,784,969 | 2,187 |
[
"WebAssembly",
"wabt"
] | Consider this snippet
```
(module
(func $f (param $y f32) (param $y1 f32) (result f32) (result f32) (result f32)
(local $y2 f32)
(local.set $y2 (f32.const 11.0))
(f32.sub (f32.const -1.0) local.get $y) ;; A
(f32.sub local.get $y local.get $y1 local.get $y2) ;; B
)
... | Compliance with 6.5.10 | https://api.github.com/repos/WebAssembly/wabt/issues/2186/comments | 3 | 2023-03-30T11:39:04Z | 2023-03-31T22:58:12Z | https://github.com/WebAssembly/wabt/issues/2186 | 1,647,445,783 | 2,186 |
[
"WebAssembly",
"wabt"
] | ### Describe the bug
Certain `hang.wasm` causes `wasm2c` an infinite loop. `wasm2c` tries to access a memory that is not permitted instead of providing `type mismatch` error for a while.
`wasm2c --version`: 1.0.32 (git~1.0.32-46-g47a589a1)
--------------------------
### Content of the file that causes the iss... | wasm2c hangs on certain inputs and cannot finish execution for a while. | https://api.github.com/repos/WebAssembly/wabt/issues/2180/comments | 5 | 2023-03-27T20:41:27Z | 2023-03-31T17:02:49Z | https://github.com/WebAssembly/wabt/issues/2180 | 1,642,781,849 | 2,180 |
[
"WebAssembly",
"wabt"
] | ```c
/* Construct the module instance. */
wasm2c_fac_instantiate(&fac);
````
this api changed, use `wasm2c_fac_instantiate(&db2, NULL, NULL);` get this linker error:
```sh
lld: error: undefined symbol: _w2c_env_0x5F_main_argc_argv
>>> referenced by sqlite.c:327248 (test.c:327248)
>>> db2... | wasm2c docs expired, build with linker error | https://api.github.com/repos/WebAssembly/wabt/issues/2175/comments | 9 | 2023-03-15T13:22:54Z | 2023-03-16T07:48:16Z | https://github.com/WebAssembly/wabt/issues/2175 | 1,625,523,997 | 2,175 |
[
"WebAssembly",
"wabt"
] | I want build `libwasm-rt-impl.a` without `libwabt.a` for cross build. (libwabt.a not needed)
try build with `-DBUILD_TESTS=OFF -DWITH_WASI=OFF -DBUILD_TOOLS=OFF -DBUILD_LIBWASM=OFF `, can not turn it off.
| need a cmake option turn off build libwabt.a ( libwasm-rt-impl.a only) | https://api.github.com/repos/WebAssembly/wabt/issues/2174/comments | 1 | 2023-03-15T06:16:13Z | 2023-03-15T06:34:41Z | https://github.com/WebAssembly/wabt/issues/2174 | 1,624,829,637 | 2,174 |
[
"WebAssembly",
"wabt"
] | ### Describe the bug
'@' before a quote (") causes a libc++abi.dylib crash while converting ".wat" format into ".wasm" format using wat2wasm.
`wat2wasm --version`: 1.0.32 (git~1.0.32-35-g9990b0cf)
---------------
The following minimized code causes wat2wasm to crash.
```
(module (memory $mem 1)
;;(@... | '@' before a quote (") causes a libc++abi.dylib crash using wat2wasm. | https://api.github.com/repos/WebAssembly/wabt/issues/2165/comments | 2 | 2023-03-09T23:07:30Z | 2023-06-17T09:47:53Z | https://github.com/WebAssembly/wabt/issues/2165 | 1,618,118,032 | 2,165 |
[
"WebAssembly",
"wabt"
] | Error message:
`wasm-decompile: /home/kangm/code/wabt/src/decompiler.cc:688: std::__cxx11::string wabt::Decompiler::InitExp(const ExprList&): Assertion `!el.empty()' failed.`
PR:
https://github.com/WebAssembly/wabt/pull/2163 | wasm-decompile fails on wasm files containing passive data segments | https://api.github.com/repos/WebAssembly/wabt/issues/2164/comments | 0 | 2023-03-08T11:22:30Z | 2023-07-30T23:27:39Z | https://github.com/WebAssembly/wabt/issues/2164 | 1,615,105,948 | 2,164 |
[
"WebAssembly",
"wabt"
] | Some functions return a `Result` enum - and because the return value is taken up by the `Result` value, these functions also pass in a pointer to write the intended 'output' into - a good example are the `Parse*` functions in [`literal.cc`](https://github.com/WebAssembly/wabt/blob/main/src/literal.cc).
Personally, I... | Lexer: Refactor Result and make functions more pure | https://api.github.com/repos/WebAssembly/wabt/issues/2159/comments | 3 | 2023-03-05T15:42:12Z | 2023-04-13T18:45:17Z | https://github.com/WebAssembly/wabt/issues/2159 | 1,610,249,088 | 2,159 |
[
"WebAssembly",
"wabt"
] | Can wasm-interp be built for wasm?
Solving for https://github.com/WebAssembly/binaryen/issues/5530 | wasm-interp for the web | https://api.github.com/repos/WebAssembly/wabt/issues/2157/comments | 13 | 2023-03-03T22:33:08Z | 2023-03-05T18:24:09Z | https://github.com/WebAssembly/wabt/issues/2157 | 1,609,337,471 | 2,157 |
[
"WebAssembly",
"wabt"
] | Is there way to tell wasm-strip not to remove the calls that are being called with Module.ccall. Currently it strips everything and then javascript cannot call the wasm functions :-) | wasm-strip removes also names that are being used for Module.ccall | https://api.github.com/repos/WebAssembly/wabt/issues/2156/comments | 9 | 2023-03-02T06:17:55Z | 2023-03-03T19:14:13Z | https://github.com/WebAssembly/wabt/issues/2156 | 1,606,178,387 | 2,156 |
[
"WebAssembly",
"wabt"
] | Hi,
I used emcsripten to compile a c/c++ program to webassembly. It generated some wasm files.
Now, I want to identify which source code (.c/.cpp file) generated a wasm file? How can I identify?
I also used wasm2wat, wasm-decompile, wasm-objdump, and wasm2c to identify a link to a source code, but I couldn't fi... | How to find source code that generated a wasm file? | https://api.github.com/repos/WebAssembly/wabt/issues/2155/comments | 2 | 2023-02-28T06:53:26Z | 2023-03-07T05:41:07Z | https://github.com/WebAssembly/wabt/issues/2155 | 1,602,470,952 | 2,155 |
[
"WebAssembly",
"wabt"
] | ```
===> Building for wabt-1.0.32
[ 0% 7/137] /usr/local/libexec/ccache/c++ -D__STDC_FORMAT_MACROS=1 -D__STDC_LIMIT_MACROS=1 -Dwabt_fuzz_EXPORTS -O2 -pipe -fstack-protector-strong -isystem /usr/local/include -fno-strict-aliasing -isystem /usr/local/include -Wold-style-cast -fno-exceptions -O2 -pipe -fstack-protec... | Build with BUILD_FUZZ_TOOLS=ON fails: fatal error: 'wabt/binary-reader-logging.h' file not found | https://api.github.com/repos/WebAssembly/wabt/issues/2153/comments | 0 | 2023-02-28T02:38:18Z | 2023-03-02T01:43:29Z | https://github.com/WebAssembly/wabt/issues/2153 | 1,602,268,911 | 2,153 |
[
"WebAssembly",
"wabt"
] | oss-fuzz has discovered that if a module includes an extremely deep series of nested blocks (e.g. a huge number of nested `if` instructions, each in the parent's "true" block), that `wasm2wat` will crash when trying to run the `Module` destructor, just because each `Block` recursively runs the destructor of its child `... | Very deep nested labels can cause BinaryReaderIR to crash (stack overflow in Module destructor) | https://api.github.com/repos/WebAssembly/wabt/issues/2151/comments | 0 | 2023-02-27T19:25:58Z | 2023-03-14T06:18:40Z | https://github.com/WebAssembly/wabt/issues/2151 | 1,601,810,647 | 2,151 |
[
"WebAssembly",
"wabt"
] | While wasm-objdump can read the Type section according to the GC proposal:
```
Type[2]:
- type[0] () -> i64
- type[1] (struct (mut i32) (mut i32) (mut i32))
```
It fails reading the Code sections new 0xFB prefix:
`error: 0x64 missing opcode callback at 0x55 (0xfb=<invalid>)`
where `wasm-dis` outputs:
``... | wasm-objdump GC proposal | https://api.github.com/repos/WebAssembly/wabt/issues/2145/comments | 1 | 2023-02-14T21:33:39Z | 2023-02-14T21:40:47Z | https://github.com/WebAssembly/wabt/issues/2145 | 1,584,861,502 | 2,145 |
[
"WebAssembly",
"wabt"
] | It would also be great to have support for [WebAssembly / stringref](https://github.com/WebAssembly/stringref) proposal | [Feature requiest] stringref proposal | https://api.github.com/repos/WebAssembly/wabt/issues/2144/comments | 1 | 2023-02-13T13:05:54Z | 2023-03-14T06:23:37Z | https://github.com/WebAssembly/wabt/issues/2144 | 1,582,319,317 | 2,144 |
[
"WebAssembly",
"wabt"
] | Hi~
After reading src code of wasm2c, I found that wasm2c mainly uses enumeration to match and generate C code.And this makes the generated C code look similar to wat.
eg. if I want generated c code like this:
```
if (*hex == '#') {
hex++;
}
```
for now, it would generated like this:
```static v... | Make wasm2c more readable | https://api.github.com/repos/WebAssembly/wabt/issues/2141/comments | 4 | 2023-02-03T13:04:02Z | 2023-02-04T11:45:39Z | https://github.com/WebAssembly/wabt/issues/2141 | 1,569,811,564 | 2,141 |
[
"WebAssembly",
"wabt"
] | ## Environment:
Host: Windows 10, x86_64
Target: Windows 11, ARM64.
Compiler:
Visual Studio 2022 Version 17.4.4
WABT Version:
```shell
git rev-parse HEAD
8a7b7497bdf78f9099f8d5a3a2c9bde87ddd52da
```
## Reproduce steps:
```shell
mkdir build_win_arm
cd build_win_arm
cmake -G "Visual Studio 17 2022" -A A... | WABT is not supported on ARM64 windows | https://api.github.com/repos/WebAssembly/wabt/issues/2139/comments | 0 | 2023-02-02T06:13:49Z | 2023-02-09T02:47:55Z | https://github.com/WebAssembly/wabt/issues/2139 | 1,567,393,179 | 2,139 |
[
"WebAssembly",
"wabt"
] | I've been looking over at using the wabt JS API, as well as [wabt.js](https://github.com/AssemblyScript/wabt.js).
I'm a little confused about why the compiled wabt toolkit is essentially exported as function that returns a promise which resolves to a `WabtModule` class.
This kinda means that for projects incremen... | Why is the JS api module- and promise-based? / Alternative non-`Promise` Emscripten compilation path | https://api.github.com/repos/WebAssembly/wabt/issues/2138/comments | 2 | 2023-02-01T07:55:25Z | 2023-02-08T06:38:04Z | https://github.com/WebAssembly/wabt/issues/2138 | 1,565,615,123 | 2,138 |
[
"WebAssembly",
"wabt"
] | This module (assembled with `--debug-names`) can cause an assertion failure in wasm2c:
```wat
(module
(func (param $B0 i32)
(block
(br 0))))
```
The problem is that the `$B0` param conflicts with the generated name of the block label. This is similar to #2035. We may need to split out labels from `D... | wasm2c local names for params can conflict with names for labels | https://api.github.com/repos/WebAssembly/wabt/issues/2136/comments | 0 | 2023-01-31T07:40:51Z | 2023-02-07T16:50:08Z | https://github.com/WebAssembly/wabt/issues/2136 | 1,563,813,009 | 2,136 |
[
"WebAssembly",
"wabt"
] | Building wabt 1.0.32 and running testsuite with gcc 13.0.0 on Fedora rawhide (development branch) yields one new test failure, on x86_64, aarch64 and ppc64le (I haven't tested on s390x or i686 yet):
```
- test/wasm2c/spec/float_exprs.txt
expected error code 0, got 1.
STDERR MISMATCH:
--- expected
+++ actu... | wasm2c/spec/float_exprs.txt fails with GCC 13.0.0 | https://api.github.com/repos/WebAssembly/wabt/issues/2130/comments | 5 | 2023-01-17T16:56:36Z | 2023-05-04T05:40:34Z | https://github.com/WebAssembly/wabt/issues/2130 | 1,536,722,347 | 2,130 |
[
"WebAssembly",
"wabt"
] | When I tried to transform .wasm file to other type file, i got the error message "invalid section size: extends past end". Is there anyone who can help?
| [Error] invalid section size: extends past end | https://api.github.com/repos/WebAssembly/wabt/issues/2128/comments | 0 | 2023-01-16T03:09:36Z | 2023-01-16T03:23:45Z | https://github.com/WebAssembly/wabt/issues/2128 | 1,534,199,705 | 2,128 |
[
"WebAssembly",
"wabt"
] | When I run `wast2json` on the `test/core/select.wast` test from https://github.com/WebAssembly/spec, I see the following failure:
```
wast2json test/core/select.wast
test/core/select.wast:526:55: error: unexpected token "result", expected an instr.
(func (result i32) unreachable select (result i32) (result))
... | wast2json fails on test/core/select.wast | https://api.github.com/repos/WebAssembly/wabt/issues/2125/comments | 3 | 2023-01-10T02:24:00Z | 2023-01-11T00:50:47Z | https://github.com/WebAssembly/wabt/issues/2125 | 1,526,655,990 | 2,125 |
[
"WebAssembly",
"wabt"
] | Not sure how feasible it would be, but it would be great if the generated C file implemented the [WebAssembly C API](https://github.com/WebAssembly/wasm-c-api/blob/main/include/wasm.h) for instantiation, dynamic enumeration of exports, integration with imports etc. for better interop with other engines. | Implement WebAssembly C API for wasm2c output | https://api.github.com/repos/WebAssembly/wabt/issues/2123/comments | 2 | 2023-01-07T15:29:51Z | 2023-01-11T09:05:02Z | https://github.com/WebAssembly/wabt/issues/2123 | 1,523,917,332 | 2,123 |
[
"WebAssembly",
"wabt"
] | When running 1.0.32 testsuite on aarch64 under Fedora 36, I get the following new failure:
```
- test/spec/relaxed-simd/relaxed_madd_nmadd.txt
expected error code 0, got 2.
STDOUT MISMATCH:
--- expected
+++ actual
@@ -1 +1,3 @@
-7/7 tests passed.
+out/test/spec/relaxed-simd/relaxed_madd_nmadd.was... | spec/relaxed-simd/relaxed_madd_nmadd.txt test fails on ARM 64-bit (aarch64), Power8 (ppc64le), z/Architecture (s390x) | https://api.github.com/repos/WebAssembly/wabt/issues/2118/comments | 2 | 2023-01-03T18:19:11Z | 2023-01-11T09:06:29Z | https://github.com/WebAssembly/wabt/issues/2118 | 1,517,758,634 | 2,118 |
[
"WebAssembly",
"wabt"
] | 0001722: error: unable to read string: section name | 这反编译出这错什么原因? [What is the reason for this error in decompilation?] | https://api.github.com/repos/WebAssembly/wabt/issues/2112/comments | 1 | 2022-12-28T14:45:26Z | 2022-12-28T17:54:46Z | https://github.com/WebAssembly/wabt/issues/2112 | 1,512,865,996 | 2,112 |
[
"WebAssembly",
"wabt"
] | If wabt was compiled for a wasi target, any wasi runtime can run it which provides flexibility both for ad-hoc CLI use (broader than the binaries on the release page) as well embedded use (without dynamic libraries)
For example, wazero could use this to keep dev dependencies light for wat based tests and also spec t... | build and publish a wasi binary on release | https://api.github.com/repos/WebAssembly/wabt/issues/2101/comments | 8 | 2022-12-14T02:32:11Z | 2023-06-12T05:15:55Z | https://github.com/WebAssembly/wabt/issues/2101 | 1,495,505,227 | 2,101 |
[
"WebAssembly",
"wabt"
] | Currently wasm-validate outputs the offending operation, however the context needs to be grep'ed manually:
```
wasm-validate main.wasm
main.wasm:000007b: error: type mismatch in i32.and, expected [i32, i32] but got [... i64, i32]
wasm-objdump main.wasm -d | grep -B3 7b
000077: 20 03 |... | option for wasm-validate to output context | https://api.github.com/repos/WebAssembly/wabt/issues/2100/comments | 0 | 2022-12-13T12:05:49Z | 2023-03-15T11:58:23Z | https://github.com/WebAssembly/wabt/issues/2100 | 1,494,103,649 | 2,100 |
[
"WebAssembly",
"wabt"
] | The `spectest_make_externref()` in [test/spec-wasm2c-prefix.c:203](https://github.com/WebAssembly/wabt/blob/main/test/spec-wasm2c-prefix.c#L203) assumes that `u64` (`uint64_t`) can be converted to `wasm_rt_externref_t` (`void *`). This is not the case on 32-bit platforms:
```
- test/regress/regress-2039.txt
expect... | wasm2c tests fail on 32-bit due to assumption that pointers are 64-bit | https://api.github.com/repos/WebAssembly/wabt/issues/2099/comments | 3 | 2022-12-11T21:37:24Z | 2023-01-08T22:21:30Z | https://github.com/WebAssembly/wabt/issues/2099 | 1,490,471,257 | 2,099 |
[
"WebAssembly",
"wabt"
] | A function type which references another function type as a parameter type corrupts the internal state of wat2wasm, causing type lookup to fail, apparently returning (-1 / 0xffffffff / 4294967295) internally. The module and output are included below. This happens both with the current HEAD of the main branch and with t... | wat2wasm internal corruption due to presence of functor type | https://api.github.com/repos/WebAssembly/wabt/issues/2098/comments | 1 | 2022-12-04T20:51:44Z | 2022-12-04T21:13:16Z | https://github.com/WebAssembly/wabt/issues/2098 | 1,475,174,777 | 2,098 |
[
"WebAssembly",
"wabt"
] | The following module
(module
(func (param (ref $T)) (result)
(nop)))
aborts in both the current main HEAD and the most recent package version on Ubuntu 20.04:
pat@quercus:~/src/crack$ ../wabt/bin/wat2wasm --version
1.0.31 (git~1.0.31-22-ged0b720c)
pat@quercus:~/src/crack$ ..... | wat2wasm aborts when function has undefined reference type in parameter | https://api.github.com/repos/WebAssembly/wabt/issues/2097/comments | 1 | 2022-12-04T19:32:27Z | 2022-12-04T21:10:26Z | https://github.com/WebAssembly/wabt/issues/2097 | 1,475,113,515 | 2,097 |
[
"WebAssembly",
"wabt"
] | 'wasm2c' is not recognized as an internal or external command,
operable program or batch file.
There is no .exe file in the project :{
| 'wasm2c' is not recognized as an internal or external command, operable program or batch file. | https://api.github.com/repos/WebAssembly/wabt/issues/2076/comments | 2 | 2022-11-27T09:47:27Z | 2022-12-01T02:15:13Z | https://github.com/WebAssembly/wabt/issues/2076 | 1,465,386,231 | 2,076 |
[
"WebAssembly",
"wabt"
] | see https://github.com/yamt/toywasm/blob/424755e4210568ed112b155000c05d772b02e989/test/run-ffmpeg.sh#L18-L22
the same wasm binary works fine on other engines listed in https://github.com/yamt/toywasm/blob/424755e4210568ed112b155000c05d772b02e989/test/run-ffmpeg.sh#L4-L8 | wasm-interp: possible misexecution issue | https://api.github.com/repos/WebAssembly/wabt/issues/2074/comments | 2 | 2022-11-19T05:58:05Z | 2022-11-19T07:04:00Z | https://github.com/WebAssembly/wabt/issues/2074 | 1,456,245,537 | 2,074 |
[
"WebAssembly",
"wabt"
] | I'm trying to release 1.0.30 packages for Fedora and I'm getting these new test failures on s390x:
```
- test/wasm2c/spec/bulk.txt
expected error code 0, got 1.
STDERR MISMATCH:
--- expected
+++ actual
@@ -0,0 +1,29 @@
+Traceback (most recent call last):
+ File "/builddir/build/BUILD/wabt-1.0.... | test failures in 1.0.30 on s390x running Fedora (36) | https://api.github.com/repos/WebAssembly/wabt/issues/2070/comments | 7 | 2022-11-16T11:05:00Z | 2022-11-22T22:13:43Z | https://github.com/WebAssembly/wabt/issues/2070 | 1,451,379,752 | 2,070 |
[
"WebAssembly",
"wabt"
] | I'm trying to track down an issue with a modified version of `wasm-interp.cc` I'm using. It's not clear whether it's a bug on my end, or a bug in interp, so I hope someone can point me to what's going wrong. I tried to strip down the interpreter to the minimal reproducing program.
I have the following WebAssembly pr... | interp: Value conditional struct field not present in release build | https://api.github.com/repos/WebAssembly/wabt/issues/2069/comments | 3 | 2022-11-16T07:56:55Z | 2022-11-16T18:47:59Z | https://github.com/WebAssembly/wabt/issues/2069 | 1,451,074,783 | 2,069 |
[
"WebAssembly",
"wabt"
] | I have a small application that uses wabt::interp. It used to run fine against the binary release of 1.0.30, but no longer does against 1.0.31 (see below). I have the same problem with the macOS binary release and the linux binary release, so it doesn't seem to be platform-specific. When I build the 1.0.31 tag myself, ... | interp issues with 1.0.31 binary release | https://api.github.com/repos/WebAssembly/wabt/issues/2068/comments | 1 | 2022-11-15T20:11:29Z | 2022-11-15T20:17:20Z | https://github.com/WebAssembly/wabt/issues/2068 | 1,450,320,964 | 2,068 |
[
"WebAssembly",
"wabt"
] | I'm interested in a new WABT build that includes the wasm2c reftypes and the CWriter in libwabt.
It's not super-urgent, but just so you know at least 1 person is waiting for a new tag ;) | Tag 1.0.31? | https://api.github.com/repos/WebAssembly/wabt/issues/2059/comments | 3 | 2022-11-13T19:38:18Z | 2022-11-15T21:58:30Z | https://github.com/WebAssembly/wabt/issues/2059 | 1,447,054,552 | 2,059 |
[
"WebAssembly",
"wabt"
] | When using `wasm2c`, the `wasm-rt-*` files are necessary to compile/link the resulting program. The WABT binary release packages come with a compiled version of wasm-rt as a static library, but this may not match the target platform for which the `wasm2c` result is used.
I therefore propose to include the necessary... | Include wasm-rt* source files in binary release packages | https://api.github.com/repos/WebAssembly/wabt/issues/2057/comments | 1 | 2022-11-12T16:43:03Z | 2022-11-13T17:19:28Z | https://github.com/WebAssembly/wabt/issues/2057 | 1,446,519,774 | 2,057 |
[
"WebAssembly",
"wabt"
] | wat2wasm: the description of this should name and call this "[web]assembler"
wasm2wat: and this as "[web]disassembler" | Naming | https://api.github.com/repos/WebAssembly/wabt/issues/2056/comments | 2 | 2022-11-12T15:32:24Z | 2022-11-15T21:59:04Z | https://github.com/WebAssembly/wabt/issues/2056 | 1,446,495,474 | 2,056 |
[
"WebAssembly",
"wabt"
] | I have the following program that reads a WASM module and immediately tries to write it again:
wabt::Errors errors;
wabt::Features features;
wabt::Module mod;
auto result = ReadBinaryIr("in.wasm", in_data, sizeof(in_data), wabt::ReadBinaryOptions(features, NULL, true, true, true), &errors,... | Assertion fails roundtripping reading/writing file | https://api.github.com/repos/WebAssembly/wabt/issues/2050/comments | 1 | 2022-11-09T18:18:58Z | 2022-11-09T19:36:19Z | https://github.com/WebAssembly/wabt/issues/2050 | 1,442,547,200 | 2,050 |
[
"WebAssembly",
"wabt"
] | wasm2c has a number of globals and statics that assume that wasm instances are only embedded in a single threaded host.
However, when using wasm2c in complex hosts like Firefox, different host threads can spin up multiple sandbox instances concurrently, invoke function in their respective sandboxes and destroy sand... | wasm2c use of globals and statics introduce race conditions in concurrent environments | https://api.github.com/repos/WebAssembly/wabt/issues/2046/comments | 9 | 2022-11-08T02:40:48Z | 2023-12-04T02:23:05Z | https://github.com/WebAssembly/wabt/issues/2046 | 1,439,361,907 | 2,046 |
[
"WebAssembly",
"wabt"
] | https://github.com/WebAssembly/wabt/blob/f25775cf7a627f3f15f00bf76dc0852e5ccf5df8/src/binary-reader-ir.cc#L1498
This can break wasm2c when running on a Wasm module with debug names (including the `throw.wast` test).
Tracking issue for regression test. | BinaryReaderIR::SetTagName puts tag names into bindings for globals | https://api.github.com/repos/WebAssembly/wabt/issues/2039/comments | 0 | 2022-11-04T20:46:19Z | 2022-11-04T21:16:00Z | https://github.com/WebAssembly/wabt/issues/2039 | 1,436,631,798 | 2,039 |
[
"WebAssembly",
"wabt"
] | wasm2c seems to have trouble if the module has duplicate debug names. E.g. this module:
```wat
(module
(memory $x 0)
(table $x 0 funcref)
)
```
processed with:
```
$ wat2wasm --debug-names -o test.wasm test.wat
$ wasm2c -o test.c test.wasm
```
correctly produces unique-ified names when it declares the ele... | wasm2c doesn't handle duplicate debug names | https://api.github.com/repos/WebAssembly/wabt/issues/2034/comments | 0 | 2022-11-02T05:17:15Z | 2022-11-30T00:17:26Z | https://github.com/WebAssembly/wabt/issues/2034 | 1,432,513,427 | 2,034 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.