issue_owner_repo listlengths 2 2 | issue_body stringlengths 0 261k ⌀ | issue_title stringlengths 1 925 | issue_comments_url stringlengths 56 81 | issue_comments_count int64 0 2.5k | issue_created_at stringlengths 20 20 | issue_updated_at stringlengths 20 20 | issue_html_url stringlengths 37 62 | issue_github_id int64 387k 2.91B | issue_number int64 1 131k |
|---|---|---|---|---|---|---|---|---|---|
[
"llvm",
"llvm-project"
] | | | |
| --- | --- |
| Bugzilla Link | [4](https://llvm.org/bz4) |
| Resolution | FIXED |
| Resolved on | Feb 22, 2010 12:42 |
| Version | trunk |
| OS | Linux |
| Depends On | llvm/llvm-bugzilla-archive#41 |
## Extended Description
For an unknown reason, LLC produced executables randomly segfault. This does
not e... | LLC Produced executables randomly crash | https://api.github.com/repos/llvm/llvm-project/issues/376/comments | 12 | 2003-10-07T20:43:59Z | 2021-12-01T18:45:30Z | https://github.com/llvm/llvm-project/issues/376 | 1,068,755,642 | 376 |
[
"llvm",
"llvm-project"
] | | | |
| --- | --- |
| Bugzilla Link | [3](https://llvm.org/bz3) |
| Resolution | WORKSFORME |
| Resolved on | Sep 19, 2018 06:24 |
| Version | trunk |
| OS | Linux |
## Extended Description
"gccld foo.a foo.a" fails with multiple symbol definition bugs, whereas "gccld
-lfoo -lfoo" works properly. | Linking two .a files explicitly on the command line fails | https://api.github.com/repos/llvm/llvm-project/issues/375/comments | 24 | 2003-10-07T20:40:53Z | 2022-01-20T01:59:04Z | https://github.com/llvm/llvm-project/issues/375 | 1,068,755,629 | 375 |
[
"llvm",
"llvm-project"
] | | | |
| --- | --- |
| Bugzilla Link | [2](https://llvm.org/bz2) |
| Resolution | FIXED |
| Resolved on | Feb 22, 2010 12:43 |
| Version | unspecified |
| OS | Linux |
| Reporter | LLVM Bugzilla Contributor |
## Extended Description
Change the header on every page to say "LLVM bugs" instead of "Bugzilla". | Customize Bugzilla to have some LLVM flavah | https://api.github.com/repos/llvm/llvm-project/issues/374/comments | 49 | 2003-10-07T20:11:05Z | 2021-12-01T18:45:28Z | https://github.com/llvm/llvm-project/issues/374 | 1,068,755,610 | 374 |
[
"llvm",
"llvm-project"
] | | | |
| --- | --- |
| Bugzilla Link | [1](https://llvm.org/bz1) |
| Resolution | FIXED |
| Resolved on | Feb 22, 2010 12:40 |
| Version | unspecified |
| OS | Linux |
| Reporter | LLVM Bugzilla Contributor |
## Extended Description
Add versions "1.0" and "trunk" to all our supported products.
Remove the "unspecifie... | Need to add product version numbers | https://api.github.com/repos/llvm/llvm-project/issues/373/comments | 86 | 2003-10-07T20:09:57Z | 2021-12-02T06:54:21Z | https://github.com/llvm/llvm-project/issues/373 | 1,068,755,588 | 373 |
[
"WebAssembly",
"wabt"
] | Is it possible to get `wabt::WastParser::ParseScript` to return the contents of `(module binary ...)` modules even if those modules are invalid?
My use case is that I'm helping to write a WASM JIT compiler and I want to exercise it with invalid inputs.
E.g. if the module looks like `(module binary "\00")`, I want to ... | Parse invalid binary modules | https://api.github.com/repos/WebAssembly/wabt/issues/2561/comments | 2 | 2025-03-11T06:17:51Z | 2025-03-11T16:51:55Z | https://github.com/WebAssembly/wabt/issues/2561 | 2,909,273,266 | 2,561 |
[
"WebAssembly",
"wabt"
] | I noticed that `webassemblyjs`'s `instantiate()` does not accept a `WebAssembly.Module` in `bufferSource`: https://github.com/xtuc/webassemblyjs/blob/master/packages/webassemblyjs/src/index.js#L30
But in [the MDN docs](https://developer.mozilla.org/en-US/docs/WebAssembly/Reference/JavaScript_interface/instantiate_stat... | `webassemblyjs`'s `instantiate()` does not accept a `WebAssembly.Module` | https://api.github.com/repos/WebAssembly/wabt/issues/2559/comments | 2 | 2025-03-06T18:54:59Z | 2025-03-06T19:05:11Z | https://github.com/WebAssembly/wabt/issues/2559 | 2,901,182,787 | 2,559 |
[
"WebAssembly",
"wabt"
] |
## Affected Projects
wabt v1.0.36 ([https://github.com/WebAssembly/wabt](https://github.com/WebAssembly/wabt))
## Problem Type
CWE-122: Heap-based Buffer Overflow
## Description
### Details
A heap-buffer-overflow vulnerability arises in the wabt::interp::(anonymous namespace)::BinaryReaderInterp::GetReturnCallDropKeep... | A Heap-based Buffer Overflow in wabt::interp::(anonymous namespace)::BinaryReaderInterp::GetReturnCallDropKeepCount | https://api.github.com/repos/WebAssembly/wabt/issues/2557/comments | 0 | 2025-03-06T13:22:34Z | 2025-03-06T13:22:34Z | https://github.com/WebAssembly/wabt/issues/2557 | 2,900,405,517 | 2,557 |
[
"WebAssembly",
"wabt"
] | Hi,
this is an issue found by fuzzing the current main branch.
## Affected Projects
wabt v1.0.36 ([https://github.com/WebAssembly/wabt](https://github.com/WebAssembly/wabt))
## Problem Type
CWE-122: Heap-based Buffer Overflow
## Description
### Details
A heap-buffer-overflow vulnerability arises in the wabt::interp::(... | A Heap-based Buffer Overflow in wabt::interp::(anonymous namespace)::BinaryReaderInterp::OnExport | https://api.github.com/repos/WebAssembly/wabt/issues/2556/comments | 1 | 2025-03-06T07:33:28Z | 2025-03-06T12:11:46Z | https://github.com/WebAssembly/wabt/issues/2556 | 2,899,598,349 | 2,556 |
[
"WebAssembly",
"wabt"
] | I would like to parse some test files using wabt from the function reference (Phase 5) proposal such as `call_ref.wast`.
https://github.com/WebAssembly/function-references/blob/main/test/core/call_ref.wast
I have enabled the feature with `--enable-function-references`.
However, I get errors such as:
```
call_ref.was... | Function references support | https://api.github.com/repos/WebAssembly/wabt/issues/2551/comments | 5 | 2025-03-03T14:24:25Z | 2025-03-11T10:52:25Z | https://github.com/WebAssembly/wabt/issues/2551 | 2,891,400,203 | 2,551 |
[
"WebAssembly",
"wabt"
] | Hi 👋 !
Would it be possible to have a release including the new fixes and improvements around Exception Handling?
Thanks a lot in advance! | release | https://api.github.com/repos/WebAssembly/wabt/issues/2550/comments | 3 | 2025-03-03T13:36:28Z | 2025-03-04T16:58:17Z | https://github.com/WebAssembly/wabt/issues/2550 | 2,891,278,747 | 2,550 |
[
"WebAssembly",
"wabt"
] | Building a library for sandboxing results in a 6MB wasm2c source file which results in my compiler running out of memory(>24GB). | wasm2c: Support outputting multiple source files? | https://api.github.com/repos/WebAssembly/wabt/issues/2547/comments | 1 | 2025-02-24T19:08:33Z | 2025-02-25T20:43:13Z | https://github.com/WebAssembly/wabt/issues/2547 | 2,875,906,816 | 2,547 |
[
"WebAssembly",
"wabt"
] | Hi,
I'm just setting up my new build machine, with Ubuntu 24.04 and CMake 3.28.3, and running 'make' fails to configure because of lots of errors like this:
```
CMake Error at CMakeLists.txt:510 (add_executable):
The install of the spectest-interp target requires changing an RPATH from
the build tree, but this is ... | Configure failure with CMake | https://api.github.com/repos/WebAssembly/wabt/issues/2544/comments | 3 | 2025-02-17T11:47:11Z | 2025-02-18T16:31:24Z | https://github.com/WebAssembly/wabt/issues/2544 | 2,857,615,907 | 2,544 |
[
"WebAssembly",
"wabt"
] | Hi,
wabt, as built on debian, fails on mips64el architecture:
https://buildd.debian.org/status/fetch.php?pkg=wabt&arch=mips64el&ver=1.0.34%2Bdsfg2%2B%7Ecs1.0.32-4&stamp=1739635385&raw=0
but it doesn't fail on [loong64](https://buildd.debian.org/status/fetch.php?pkg=wabt&arch=loong64&ver=1.0.34%2Bdsfg2%2B%7Ecs1.0.32-4... | mips test/interp/simd-binary.txt simd-unary.txt test failures | https://api.github.com/repos/WebAssembly/wabt/issues/2543/comments | 8 | 2025-02-17T09:47:30Z | 2025-02-18T00:46:04Z | https://github.com/WebAssembly/wabt/issues/2543 | 2,857,318,598 | 2,543 |
[
"WebAssembly",
"wabt"
] | When building wabt-1.0.36 with GCC 15 (Fedora 42 and rawhide) and running the testsuite on ppc64le
```
- test/wasm2c/spec/float_exprs.txt
expected error code 0, got 1.
STDERR MISMATCH:
--- expected
+++ actual
@@ -0,0 +1,8 @@
+float_exprs.wast:2238: assertion failed: in w2c_float__exprs__86__wasm_f320x2Eno_... | wasm2c/spec/float_exprs.txt test fails with GCC 15 on ppc64le and s390x | https://api.github.com/repos/WebAssembly/wabt/issues/2542/comments | 16 | 2025-02-17T00:49:22Z | 2025-02-21T13:51:32Z | https://github.com/WebAssembly/wabt/issues/2542 | 2,856,455,586 | 2,542 |
[
"WebAssembly",
"wabt"
] | Currently, we have the following binary reader options:
```
Features features;
Stream* log_stream = nullptr;
bool read_debug_names = false;
bool stop_on_first_error = true;
bool fail_on_custom_section_error = true;
bool skip_function_bodies = false;
```
Now, `features` and `log_stream` are... fairly unive... | Binary reader options and intended use cases | https://api.github.com/repos/WebAssembly/wabt/issues/2537/comments | 2 | 2025-02-04T18:16:13Z | 2025-02-17T22:21:41Z | https://github.com/WebAssembly/wabt/issues/2537 | 2,830,975,836 | 2,537 |
[
"WebAssembly",
"wabt"
] | Hi,
I understand that the [WasmSpec](https://webassembly.github.io/spec/core/syntax/types.html) does not differentiate between signed and unsigned integer values explicitly:
> Integers are not inherently signed or unsigned; their interpretation is determined by individual operations.
However, I believe that when `wa... | Clarification on `wasm-interp` output format for `i32` values | https://api.github.com/repos/WebAssembly/wabt/issues/2536/comments | 7 | 2025-02-03T23:35:23Z | 2025-02-04T07:36:07Z | https://github.com/WebAssembly/wabt/issues/2536 | 2,828,786,154 | 2,536 |
[
"WebAssembly",
"wabt"
] | wabt::ReadBinaryOptions options;
options.skip_function_bodies = true;
wabt::Result errorCode = wabt::ReadBinaryIr("", wasmData, fileSize, options, &errors,
&module);
will got an assert
at function [Result BinaryReaderIR::EndFunctionBody(Index index)]
o... | options skip_function_bodies can not work with ReadBinaryIr | https://api.github.com/repos/WebAssembly/wabt/issues/2534/comments | 18 | 2025-01-25T12:55:01Z | 2025-01-28T11:31:36Z | https://github.com/WebAssembly/wabt/issues/2534 | 2,810,969,854 | 2,534 |
[
"WebAssembly",
"wabt"
] | Hi,
GitHub recently enabled Linux arm64 hosted runners for public repos:
https://github.blog/changelog/2025-01-16-linux-arm64-hosted-runners-now-available-for-free-in-public-repositories-public-preview/
To better enable projects using wabt in existing x86_64 GitHub Actions workflows to add arm64 CI jobs, it would be... | arm64 Ubuntu releases | https://api.github.com/repos/WebAssembly/wabt/issues/2533/comments | 2 | 2025-01-20T15:30:18Z | 2025-03-06T17:27:58Z | https://github.com/WebAssembly/wabt/issues/2533 | 2,799,580,534 | 2,533 |
[
"WebAssembly",
"wabt"
] | In the syntax for the C-like language produced by obj-decompile, the following syntax's behaviour is not documented anywhere in the WABT docs:
`identifier[x@y]`
I believe x is an offset and y is the number of bytes being indexed for a `load` instruction, but again, since there's no documentation, I do not fully under... | Undocumented syntax for wasm-decompile | https://api.github.com/repos/WebAssembly/wabt/issues/2532/comments | 0 | 2025-01-18T16:46:02Z | 2025-01-18T16:46:02Z | https://github.com/WebAssembly/wabt/issues/2532 | 2,797,070,952 | 2,532 |
[
"WebAssembly",
"wabt"
] | code example:
```wasm
;; wat2wasm --enable-gc ./test.wat
(module
(type $i32_arr (array (mut i32)) )
(func $createArray (param $len i32) (result i32)
(array.new
$i32_arr
(i32.const 42) ;; initial value
(local.get $len) ;; array len
)
... | wat2wasm doesn't support wasm GC? | https://api.github.com/repos/WebAssembly/wabt/issues/2530/comments | 1 | 2025-01-14T06:10:12Z | 2025-01-14T15:29:45Z | https://github.com/WebAssembly/wabt/issues/2530 | 2,786,344,965 | 2,530 |
[
"WebAssembly",
"wabt"
] | hi,
so i have seen that a new wasm2c was pushed to mozilla-unified/central the other day.
i noticed that the new tokenqueue class is using a member (value):
https://github.com/WebAssembly/wabt/blob/main/src/wast-parser.cc#L3824
that is not available for older mac targets.
```
3:12.54 /Users/Gagan/Download... | compatibility for older macs in wast-parser.c | https://api.github.com/repos/WebAssembly/wabt/issues/2527/comments | 14 | 2025-01-10T17:47:45Z | 2025-02-11T12:36:39Z | https://github.com/WebAssembly/wabt/issues/2527 | 2,780,736,838 | 2,527 |
[
"WebAssembly",
"wabt"
] |
`wasm-interp` does not correctly handle element segment initialization using `global.get` for non-imported globals.
### Test case
program.wasm
[program.wasm.txt](https://github.com/user-attachments/files/18361702/program.wasm.txt)
### Environment
* OS: Ubuntu 20.04
* CPU: amd64
* WABT version: 1.0.36
... | Incorrect Validation for Element Segment Initialization | https://api.github.com/repos/WebAssembly/wabt/issues/2526/comments | 0 | 2025-01-09T12:56:16Z | 2025-01-09T12:56:16Z | https://github.com/WebAssembly/wabt/issues/2526 | 2,777,768,400 | 2,526 |
[
"WebAssembly",
"wabt"
] |
`wasm-interp` does not enforce the requirement that a `catch` block must be associated with a `try` block.
### Test case
program.wasm
[program.wasm.txt](https://github.com/user-attachments/files/18348289/program.wasm.txt)
### Environment
* OS: Ubuntu 20.04
* CPU: amd64
* WABT version: 1.0.36
* Command... | Missing Validation for catch_all Instruction | https://api.github.com/repos/WebAssembly/wabt/issues/2525/comments | 1 | 2025-01-08T13:59:16Z | 2025-01-08T18:17:22Z | https://github.com/WebAssembly/wabt/issues/2525 | 2,775,471,680 | 2,525 |
[
"WebAssembly",
"wabt"
] | `wasm-interp` encounters an "Aborted (core dumped)" error when executing a WebAssembly module that contains call instructions. This issue leads to an unexpected termination of the program.
### Test case
[program.wasm.txt](https://github.com/user-attachments/files/18333089/program.wasm.txt)
### Environment
*... | Incorrect Handling of Call Instructions in wasm-interp | https://api.github.com/repos/WebAssembly/wabt/issues/2524/comments | 0 | 2025-01-07T13:28:02Z | 2025-01-07T13:28:02Z | https://github.com/WebAssembly/wabt/issues/2524 | 2,772,853,151 | 2,524 |
[
"WebAssembly",
"wabt"
] | `wasm-interp` fails to validate the type of the table used in the `call_indirect` instruction. According to the [WebAssembly specification](https://webassembly.github.io/spec/core/valid/instructions.html#valid-call-indirect), the table associated with `call_indirect` must have a `funcref` type.
### Test case
```w... | Missing Table Type Validation in call_indirect Instruction | https://api.github.com/repos/WebAssembly/wabt/issues/2523/comments | 0 | 2024-12-28T18:34:31Z | 2024-12-30T17:34:48Z | https://github.com/WebAssembly/wabt/issues/2523 | 2,761,830,526 | 2,523 |
[
"WebAssembly",
"wabt"
] | wabt currently applies no limits anywhere ever.
we would like to introduce a limits.json file that can be passed in the CLI. (we think a json would be a better fit than putting it all in the CLI.) like `--limits limits.json`.
the hard part is enforcing the limits tbh... but anyway. | Limits | https://api.github.com/repos/WebAssembly/wabt/issues/2522/comments | 6 | 2024-12-26T21:19:18Z | 2024-12-28T16:36:14Z | https://github.com/WebAssembly/wabt/issues/2522 | 2,760,152,550 | 2,522 |
[
"WebAssembly",
"wabt"
] | Kindly include a `wasm2c` example where the input is a WASM produced by Bytecode Alliance's Javy. There's no roadmap for compiling C output by `wasm2c` to an executable where we need to include `wasi_snapshot_preview1` in the process.
cc @shravanrn @sbc100 @keithw | wasm2c example for Bytecode Alliance's Javy | https://api.github.com/repos/WebAssembly/wabt/issues/2521/comments | 23 | 2024-12-20T02:54:14Z | 2025-01-17T03:42:19Z | https://github.com/WebAssembly/wabt/issues/2521 | 2,751,811,833 | 2,521 |
[
"WebAssembly",
"wabt"
] | presumably it should be possible to use wasm2c modules within signal handlers (but not across them). should this be an officially supported use-case? | wasm2c modules in signal handlers | https://api.github.com/repos/WebAssembly/wabt/issues/2519/comments | 2 | 2024-12-06T12:38:47Z | 2025-01-07T12:43:30Z | https://github.com/WebAssembly/wabt/issues/2519 | 2,722,965,363 | 2,519 |
[
"WebAssembly",
"wabt"
] | Take the following code:
```
(module
(memory $n 1)
(memory $m 1)
(data (memory $m) (i32.const 0))
)
```
[Compile](https://webassembly.github.io/wabt/demo/wat2wasm/).
The data section has bytes:
```
; data segment header 0
0000012: 02 ; segment flags
0000013: 4... | wat2wasm: data section memory index | https://api.github.com/repos/WebAssembly/wabt/issues/2518/comments | 5 | 2024-12-06T04:20:20Z | 2024-12-08T02:44:59Z | https://github.com/WebAssembly/wabt/issues/2518 | 2,722,016,885 | 2,518 |
[
"WebAssembly",
"wabt"
] | Hello, I encountered some problems when I'm trying to use wasm2wat.
I tried to use wasm2wat to convert some wasm file(with wasmgc) to text format, but the conversion failed, giving the warning:
`000000f: error: expected valid field type (got -0x9)`
After adding the `--enable-gc` option, I got the same error. Then I ... | Something wrong with wasm to wat conversion. | https://api.github.com/repos/WebAssembly/wabt/issues/2511/comments | 2 | 2024-11-20T02:48:59Z | 2024-11-20T03:04:19Z | https://github.com/WebAssembly/wabt/issues/2511 | 2,674,128,490 | 2,511 |
[
"WebAssembly",
"wabt"
] | - test/regress/wasm2c-ehv3-setjmp-volatile.txt
expected error code 0, got 250.
STDERR MISMATCH:
--- expected
+++ actual
@@ -0,0 +1 @@
+sigaltstack failed: Invalid argument
- test/wasm2c/spec/exception-handling/throw.txt ... | test failures on aarm64 | https://api.github.com/repos/WebAssembly/wabt/issues/2481/comments | 4 | 2024-10-02T10:53:18Z | 2025-01-07T12:37:32Z | https://github.com/WebAssembly/wabt/issues/2481 | 2,561,256,008 | 2,481 |
[
"WebAssembly",
"wabt"
] | It's quite inconvenient to find functions by indexes right now, as they are transformed. Also might be nice to add a comment with index as `wasm2wat` does `(;123;)`
https://github.com/WebAssembly/wabt/blob/790bc0472552d80671bdf99ba7652876c463d526/src/tools/wasm-decompile.cc#L89 | wasm-decompile: expose NameOpts::None as arg | https://api.github.com/repos/WebAssembly/wabt/issues/2477/comments | 1 | 2024-09-29T21:20:04Z | 2024-09-30T00:45:13Z | https://github.com/WebAssembly/wabt/issues/2477 | 2,555,160,897 | 2,477 |
[
"WebAssembly",
"wabt"
] | hey @takikawa (noticed you wrote exception handling support for the interpreter) would you have any idea why this test: https://github.com/WebAssembly/exception-handling/pull/332
```wast
(module
(tag $e0)
(func $longjmp-bait (throw $e0))
(func (export "setjmp-bait") (param $return-early i32) (result i32)
... | weird bug with exception handling (interpreter) | https://api.github.com/repos/WebAssembly/wabt/issues/2476/comments | 1 | 2024-09-27T01:45:04Z | 2024-10-01T22:56:24Z | https://github.com/WebAssembly/wabt/issues/2476 | 2,551,820,274 | 2,476 |
[
"WebAssembly",
"wabt"
] | Hi wabt team,
Recently I have been testing the decompile tool chain of WebAssembly. This is conducted by comparing the results of a C program:
- compile into WASM, decompile with `wasm-decompile`, rewrite syntax and re-compile into native binary.
- directly compile into native binary.
A few execution discrepa... | wasm-decompile decompile error | https://api.github.com/repos/WebAssembly/wabt/issues/2475/comments | 2 | 2024-09-26T21:24:12Z | 2024-09-26T21:47:31Z | https://github.com/WebAssembly/wabt/issues/2475 | 2,551,555,590 | 2,475 |
[
"WebAssembly",
"wabt"
] | When I was trying to write EOS contract, which use wasm to compilered, I found that uninitialized local var seem to be optimised. For example, the result, when added to any number and uninitialized local variable `a1`, is printed as zero.
The test code as follows:
```
#include <eosio/eosio.hpp>
using namespace e... | Will uninitialized local var be optimised? | https://api.github.com/repos/WebAssembly/wabt/issues/2473/comments | 3 | 2024-09-24T11:54:25Z | 2024-09-25T02:10:55Z | https://github.com/WebAssembly/wabt/issues/2473 | 2,545,185,862 | 2,473 |
[
"WebAssembly",
"wabt"
] | test case:
```wasm
(module
(tag $e0)
(func $longjmp-bait (throw $e0))
(func (export "setjmp-bait") (param $return-early i32) (result i32)
(local $value i32)
(try $try
(do
(br_if $try (local.get $return-early))
(local.set $value (i32.const 1))
(call $longjmp-bait)... | wasm2c: UB in exception-handling | https://api.github.com/repos/WebAssembly/wabt/issues/2469/comments | 0 | 2024-09-22T01:03:18Z | 2024-10-02T00:28:20Z | https://github.com/WebAssembly/wabt/issues/2469 | 2,540,584,028 | 2,469 |
[
"WebAssembly",
"wabt"
] | wouldn't it be better to just remove RunResult altogether? no RunResult, no bugs!
(more seriously: there are 2 different ways to convey traps currently. would it be feasible to unify them?)
consider this a "TODO" item. (if you could apply a label to this issue, that would be neat.) | Remove RunResult | https://api.github.com/repos/WebAssembly/wabt/issues/2467/comments | 0 | 2024-09-18T18:19:37Z | 2024-09-18T18:19:37Z | https://github.com/WebAssembly/wabt/issues/2467 | 2,534,381,288 | 2,467 |
[
"WebAssembly",
"wabt"
] | Opening this issue as a narrowed-down version of https://github.com/WebAssembly/wabt/issues/1949 to track freestanding-related questions.
I didn't end up using wasm2c in the original use case mentioned there for reasons completely unrelated to wasm, but I very recently considered using it for another task, again in ... | wasm2c in freestanding environment | https://api.github.com/repos/WebAssembly/wabt/issues/2460/comments | 2 | 2024-09-10T13:48:19Z | 2024-09-11T10:20:40Z | https://github.com/WebAssembly/wabt/issues/2460 | 2,516,537,577 | 2,460 |
[
"WebAssembly",
"wabt"
] | I tried running wast2json over a wast file with keywords from the latest exception proposal and it failed, taking a look at the lexer I can see it is based on the old implementation and doesn't understand instructions like try_table. It might be worth removing it from the support table or maybe annotating it to say the... | Exception proposal support is the legacy implementation | https://api.github.com/repos/WebAssembly/wabt/issues/2459/comments | 0 | 2024-09-09T18:49:01Z | 2024-09-09T18:49:01Z | https://github.com/WebAssembly/wabt/issues/2459 | 2,514,673,784 | 2,459 |
[
"WebAssembly",
"wabt"
] | wasm-interp --enable-exceptions test
```sh
error initializing module: invalid import "env.saveSetjmp"
``` | wasm-interp --enable-exceptions error invalid import "env.saveSetjmp" | https://api.github.com/repos/WebAssembly/wabt/issues/2455/comments | 8 | 2024-08-22T11:53:36Z | 2024-08-22T15:35:50Z | https://github.com/WebAssembly/wabt/issues/2455 | 2,480,595,829 | 2,455 |
[
"WebAssembly",
"wabt"
] | See https://github.com/llvm/llvm-project/blob/e56ad22b4a41e65984d6997b2c2496a20f906d1d/llvm/include/llvm/BinaryFormat/WasmRelocs.def#L27-L31 and https://github.com/WebAssembly/wabt/blob/1edeaf2948b4afd711e50ba2007ee44503cd80fe/src/common.cc#L46-L59
I hit it specifically with `R_WASM_FUNCTION_INDEX_I32`. This affects... | Missing support for the (somewhat) recently added relocation types | https://api.github.com/repos/WebAssembly/wabt/issues/2454/comments | 2 | 2024-08-20T17:59:02Z | 2024-08-29T16:10:49Z | https://github.com/WebAssembly/wabt/issues/2454 | 2,476,223,520 | 2,454 |
[
"WebAssembly",
"wabt"
] | The following module fails to compile:
```wasm
(module
(func (param externref) (result i32)
(ref.is_null)
)
)
```
Running `wat2wasm` on this leads to an exit code if 1, but no proper error message. Debugging with GDB shows that the typechecker throws an error here:
https://github.com/WebAss... | Module fails to compile without a proper error message | https://api.github.com/repos/WebAssembly/wabt/issues/2453/comments | 4 | 2024-08-15T17:05:33Z | 2024-09-23T20:55:23Z | https://github.com/WebAssembly/wabt/issues/2453 | 2,468,500,224 | 2,453 |
[
"WebAssembly",
"wabt"
] | `wasm-rt-impl-tableops.inc` has been [split off from `wasm2c/wasm-rt-impl.c`](https://github.com/WebAssembly/wabt/commit/49950cbcb8e3729cd056f1f76ee4000dbcbe309f), but this file is not installed in the installation dir. This means that `wasm-rt-impl.c` is no longer complete in installed packages.
E.g., on Homebrew:
... | `wasm-rt-impl-tableops.inc` missing from packages | https://api.github.com/repos/WebAssembly/wabt/issues/2451/comments | 0 | 2024-08-10T19:23:15Z | 2024-08-11T17:13:09Z | https://github.com/WebAssembly/wabt/issues/2451 | 2,459,263,081 | 2,451 |
[
"WebAssembly",
"wabt"
] | I get this error trying to decompile.
00002fd: error: memory may not be shared: threads not allowed
| 00002fd: error: memory may not be shared: threads not allowed | https://api.github.com/repos/WebAssembly/wabt/issues/2450/comments | 2 | 2024-08-09T00:51:06Z | 2024-10-21T22:15:48Z | https://github.com/WebAssembly/wabt/issues/2450 | 2,456,897,150 | 2,450 |
[
"WebAssembly",
"wabt"
] | When `wabt` depends on OpenSSL, it fails to `find_dependency()` the package in its config files. This can be observed when installing `wabt` via Homebrew; we get the error:
```
CMake Error at /opt/homebrew/lib/cmake/wabt/wabt-targets.cmake:61 (set_target_properties):
The link interface of target "wabt::wabt" con... | CMake missing OpenSSL dependency | https://api.github.com/repos/WebAssembly/wabt/issues/2446/comments | 7 | 2024-07-24T21:21:03Z | 2024-07-31T17:04:30Z | https://github.com/WebAssembly/wabt/issues/2446 | 2,428,496,705 | 2,446 |
[
"WebAssembly",
"wabt"
] | GIT revision: ed1ce97e
Built with `USE_ASAN=ON`
Run: `./build/wat2wasm test.wat`
Test:
```wat
(module quote "\7c")
```
Backtrace:
```
AddressSanitizer:DEADLYSIGNAL
=================================================================
==1100246==ERROR: AddressSanitizer: SEGV on unknown address 0x000000000000 (... | SEGV in wabt::Module::operator= | https://api.github.com/repos/WebAssembly/wabt/issues/2445/comments | 0 | 2024-07-23T11:16:12Z | 2024-07-23T11:16:12Z | https://github.com/WebAssembly/wabt/issues/2445 | 2,424,937,358 | 2,445 |
[
"WebAssembly",
"wabt"
] | Hello all,
I've converted a wasm file I found online to C headers and source. `./wasm2c fac.wasm -o fac.c`.
I used the example `main.c`to build a starting point, but the compiler complains that I'm missing two arguments:
```c
void wasm2c_fac_instantiate(w2c_fac* instance, struct w2c_env* w2c_env_instance, struct w2... | [wasm2c] too few arguments to function `wasm2c_fac_instantiate` | https://api.github.com/repos/WebAssembly/wabt/issues/2442/comments | 3 | 2024-07-18T07:27:53Z | 2024-07-23T04:53:58Z | https://github.com/WebAssembly/wabt/issues/2442 | 2,415,596,596 | 2,442 |
[
"WebAssembly",
"wabt"
] | ## Version
commit [4beb525](https://github.com/WebAssembly/wabt/commit/4beb52501f863f1cbd92e0ce4879f04f473935b5)
Author: Peng Qian messi.qp711@gmail.com
Date: Wen Jun 10:48:12 2024
## Compile
```
cd wabt
mkdir build
cd build
cmake -DCMAKE_CXX_FLAGS="-fsanitize=address -g" -DCMAKE_C_FLAGS="-fsanitize=address... | Invalid Read Memory in wabt::interp | https://api.github.com/repos/WebAssembly/wabt/issues/2431/comments | 1 | 2024-06-19T02:56:19Z | 2024-09-24T00:46:04Z | https://github.com/WebAssembly/wabt/issues/2431 | 2,361,143,630 | 2,431 |
[
"WebAssembly",
"wabt"
] | ## Version
commit [4beb525](https://github.com/WebAssembly/wabt/commit/4beb52501f863f1cbd92e0ce4879f04f473935b5)
Author: Peng Qian messi.qp711@gmail.com
Date: Tue Jun 15:08:05 2024
### Compile
```
cd wabt
mkdir build
cd build
cmake -DCMAKE_CXX_FLAGS="-fsanitize=address -g" -DCMAKE_C_FLAGS="-fsanitize=addres... | Allocator is out of memory in wasm-interp | https://api.github.com/repos/WebAssembly/wabt/issues/2430/comments | 3 | 2024-06-18T07:15:33Z | 2024-06-27T15:19:01Z | https://github.com/WebAssembly/wabt/issues/2430 | 2,359,120,145 | 2,430 |
[
"WebAssembly",
"wabt"
] | I'm not sure if the usage of cmake is correct, this is the command I ran, and I got a file not found error, please help me, thank you.
cmake --build .. --config DEBUG --target install
cmake .. -DCMAKE_BUILD_TYPE=DEBUG -DCMAKE_INSTALL_PREFIX=..\..\ -G "Visual Studio 2022"
“picosha2.h”: No such file or directory... | “picosha2.h”: No such file or directory | https://api.github.com/repos/WebAssembly/wabt/issues/2429/comments | 2 | 2024-06-11T16:32:30Z | 2024-06-24T20:46:45Z | https://github.com/WebAssembly/wabt/issues/2429 | 2,346,845,110 | 2,429 |
[
"WebAssembly",
"wabt"
] | I was trying out `wasm_rt_impl_try` from the `wasm-rt-impl.h` header when I got the following error:
```
src/wasm-rt-impl.h:59:32: error: 'wasm_rt_set_unwind_target' was not declared in this scope
59 | (WASM_RT_SAVE_STACK_DEPTH(), wasm_rt_set_unwind_target(&g_wasm_rt_jmp_buf), \
| ... | [wasm2c] catching traps without exception runtime | https://api.github.com/repos/WebAssembly/wabt/issues/2427/comments | 1 | 2024-05-30T19:11:13Z | 2025-01-07T12:50:10Z | https://github.com/WebAssembly/wabt/issues/2427 | 2,326,379,108 | 2,427 |
[
"WebAssembly",
"wabt"
] | When I try to compile this module
```
(module $empty)
```
with
```
wasm2wat --version
wat2wasm empty.wat
wasm2c empty.wasm -o empty
```
I get the following error message:
```
1.0.35
terminate called after throwing an instance of 'std::out_of_range'
what(): basic_string_view::substr: __pos (which ... | wasm2c compiling minimal example issues | https://api.github.com/repos/WebAssembly/wabt/issues/2423/comments | 1 | 2024-05-20T11:40:14Z | 2024-05-20T22:42:05Z | https://github.com/WebAssembly/wabt/issues/2423 | 2,305,804,304 | 2,423 |
[
"WebAssembly",
"wabt"
] | For some reason INT_MIN is not parsing correctly under MSVC..
```
#include <stdio.h>
int main() {
double x = -2147483648;
double y = -2147483648L;
double z = -2147483648.0;
printf("%f\n", x);
printf("%f\n", y);
printf("%f\n", z);
}
```
Under MSVC this produces:
```
2147483648.000000
... | [wasm2c] Strange issue with double parsing in msvc | https://api.github.com/repos/WebAssembly/wabt/issues/2422/comments | 5 | 2024-05-14T19:15:24Z | 2024-05-14T20:13:56Z | https://github.com/WebAssembly/wabt/issues/2422 | 2,296,217,808 | 2,422 |
[
"WebAssembly",
"wabt"
] | ```console
$ make clang-release
...
[133/199] Linking CXX executable wasm2c
FAILED: wasm2c
: && /usr/bin/clang++ -Wold-style-cast -fno-exceptions -O3 -DNDEBUG -arch arm64 -arch x86_64 -isysroot /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX14.4.sdk -Wl,-search_paths_fir... | Build failed on Apple Silicon platform | https://api.github.com/repos/WebAssembly/wabt/issues/2419/comments | 5 | 2024-05-14T07:18:14Z | 2024-08-30T07:52:18Z | https://github.com/WebAssembly/wabt/issues/2419 | 2,294,624,952 | 2,419 |
[
"WebAssembly",
"wabt"
] | The following WAST test expression from [if.wast](https://github.com/WebAssembly/spec/blob/228549757b301c698c5588ec0d58b201b5777c92/test/core/if.wast#L935) miscompiles, omitting the empty else block:
```wast
(assert_invalid
(module (func $type-else-value-empty-vs-num (result i32)
(if (result i32) (i32.const... | `wast2json` miscompiles "if.wast" from the specification tests | https://api.github.com/repos/WebAssembly/wabt/issues/2417/comments | 4 | 2024-05-12T05:53:57Z | 2024-05-14T22:46:58Z | https://github.com/WebAssembly/wabt/issues/2417 | 2,291,180,539 | 2,417 |
[
"WebAssembly",
"wabt"
] | Hello I have an issue when running global.json generated from global.wast, for example global.json starts like this:
```json
{"source_filename": ".../wasm-testsuite/global.wast",
"commands": [
{"type": "module", "line": 3, "filename": "global.0.wasm"},
{"type": "assert_return", "line": 196, "action": {"typ... | Missing Import when running global.wast | https://api.github.com/repos/WebAssembly/wabt/issues/2414/comments | 1 | 2024-05-06T11:10:00Z | 2024-05-06T12:01:17Z | https://github.com/WebAssembly/wabt/issues/2414 | 2,280,628,638 | 2,414 |
[
"WebAssembly",
"wabt"
] | I started seeing this error in GH macos 14 runners.
```
/Users/runner/wabt/wabt-1.0.34/bin/wasm-strip /Users/runner/work/deno-plugin/deno-plugin/builds/deno_plugin.wasm
dyld[5490]: Library not loaded: /usr/local/opt/openssl@3/lib/libcrypto.3.dylib
Referenced from: <2A3C7B41-8AA9-3951-9D8B-AB2C7D11019A> /Users/... | Library not loaded: /usr/local/opt/openssl@3/lib/libcrypto.3.dylib | https://api.github.com/repos/WebAssembly/wabt/issues/2413/comments | 9 | 2024-05-05T06:39:23Z | 2024-08-14T02:18:04Z | https://github.com/WebAssembly/wabt/issues/2413 | 2,279,352,791 | 2,413 |
[
"WebAssembly",
"wabt"
] | Running the latest wast2json (1.0.34) on [comments.wast](https://github.com/WebAssembly/testsuite/blob/main/comments.wast) or [if.wast](https://github.com/WebAssembly/testsuite/blob/main/if.wast) fails with the following errors:
```sh
comments.wast:104:1: error: unexpected token "(", expected a binary module or ... | Wast2Json fails on the testsuite | https://api.github.com/repos/WebAssembly/wabt/issues/2410/comments | 8 | 2024-04-29T20:30:59Z | 2024-05-14T17:43:29Z | https://github.com/WebAssembly/wabt/issues/2410 | 2,269,918,653 | 2,410 |
[
"WebAssembly",
"wabt"
] | GIT revision: 356931a8
Run: ASAN_OPTIONS="handle_abort=1" ./build/wat2wasm test.wat
Test:
```wat
( elem f64 ( ) )
```
Backtrace:
```
wat2wasm: wabt/src/wast-parser.cc:3159: wabt::Result wabt::WastParser::ParseExpr(wabt::ExprList *): Assertion `!"ParseExpr should only be called when IsExpr() is true"' failed.... | wat2wasm: Assertion `!"ParseExpr should only be called when IsExpr() is true"' failed in wabt::WastParser::ParseExpr | https://api.github.com/repos/WebAssembly/wabt/issues/2408/comments | 0 | 2024-04-08T23:38:23Z | 2024-07-12T16:20:10Z | https://github.com/WebAssembly/wabt/issues/2408 | 2,232,325,548 | 2,408 |
[
"WebAssembly",
"wabt"
] | In the GC proposal, it allows using previous global value as an initializer expression.
Therefore, following wasm module is a valid module in the GC proposal.
```
;; global.wat
(mo... | Wrong type error when validating globals with gc proposal features | https://api.github.com/repos/WebAssembly/wabt/issues/2407/comments | 0 | 2024-04-02T10:15:09Z | 2024-04-03T02:33:42Z | https://github.com/WebAssembly/wabt/issues/2407 | 2,220,111,562 | 2,407 |
[
"WebAssembly",
"wabt"
] | First of all, thank you for providing these great tools.
When I try to convert component wasm file to `.wat`, it keep says:
```
0000008: error: bad wasm file version: 0x1000d (expected 0x1)
```
To reproduce, [simply follow the instruction in this doc to build the component](https://component-model.bytecodeallian... | wasm2wat: support component wasm | https://api.github.com/repos/WebAssembly/wabt/issues/2405/comments | 4 | 2024-03-25T17:20:07Z | 2025-01-14T18:49:15Z | https://github.com/WebAssembly/wabt/issues/2405 | 2,206,287,834 | 2,405 |
[
"WebAssembly",
"wabt"
] | - wabt 1.0.34
- clang 17.0.6
Extracted lines:
```
out/test/wasm2c/spec/simd_lane/simd_lane.0.c:967:6: error: loop not vectorized: the optimizer was unable to perform the requested transformation; the transformation might be disabled or specified as part of an unsupported transformation ordering [-Werror,-Wpass-fa... | Error while running testsuite (simd_lane, simd_load) "loop not vectorized" | https://api.github.com/repos/WebAssembly/wabt/issues/2403/comments | 3 | 2024-03-19T16:32:41Z | 2024-03-25T23:47:16Z | https://github.com/WebAssembly/wabt/issues/2403 | 2,195,438,788 | 2,403 |
[
"WebAssembly",
"wabt"
] | null | error initializing module: invalid import "a.a" | https://api.github.com/repos/WebAssembly/wabt/issues/2402/comments | 1 | 2024-03-18T06:15:48Z | 2024-03-18T14:04:56Z | https://github.com/WebAssembly/wabt/issues/2402 | 2,191,322,716 | 2,402 |
[
"WebAssembly",
"wabt"
] | ### Environment
```shell
OS : Linux 5.15.133.1-microsoft-standard-WSL2 #1 SMP Thu Oct 5 21:02:42 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
Commit : 9fdd024249b6b181d98a4164700ca6ee09f970d9 - 1471dffee8bf9939044b80d34256956a28138e96
Version : 1.0.33 (git~1.0.33-35-gdddc03d3)
Clang V... | Invalid Memory Read in FreeList<wabt::interp::Object*>::IsUsed() | https://api.github.com/repos/WebAssembly/wabt/issues/2398/comments | 0 | 2024-03-04T14:15:39Z | 2024-09-18T18:35:56Z | https://github.com/WebAssembly/wabt/issues/2398 | 2,166,955,848 | 2,398 |
[
"WebAssembly",
"wabt"
] | ### Environment
```shell
OS : Linux 5.15.133.1-microsoft-standard-WSL2 #1 SMP Thu Oct 5 21:02:42 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
Commit : 9fdd024249b6b181d98a4164700ca6ee09f970d9 - 1471dffee8bf9939044b80d34256956a28138e96
Version : 1.0.33 (git~1.0.33-35-gdddc03d3)
Clang V... | Out-of-Memory Program Abort in BinaryReaderInterp::OnDataCount() | https://api.github.com/repos/WebAssembly/wabt/issues/2397/comments | 0 | 2024-03-04T13:47:29Z | 2024-03-04T13:47:29Z | https://github.com/WebAssembly/wabt/issues/2397 | 2,166,891,614 | 2,397 |
[
"WebAssembly",
"wabt"
] | ### Environment
```shell
OS : Linux 5.15.133.1-microsoft-standard-WSL2 #1 SMP Thu Oct 5 21:02:42 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
Commit : 9fdd024249b6b181d98a4164700ca6ee09f970d9 - 1471dffee8bf9939044b80d34256956a28138e96
Version : 1.0.33 (git~1.0.33-35-gdddc03d3)
Clang V... | Out-of-Memory Program Abort in wabt::interp::Table::Grow() | https://api.github.com/repos/WebAssembly/wabt/issues/2396/comments | 2 | 2024-03-04T13:27:53Z | 2024-03-09T13:51:56Z | https://github.com/WebAssembly/wabt/issues/2396 | 2,166,851,608 | 2,396 |
[
"WebAssembly",
"wabt"
] | I encountered an error message when attempting to use the `wasm2wat` tool to convert a `.wasm` file generated by the [Moonbit](https://www.moonbitlang.com/) toolchain with `--target wasm-gc` into the `.wat` format. The error message indicated an unexpected type form. Here are the [wasm file](https://github.com/WebAssem... | Error using wasm2wat on a wasm file generated by Moonbit: "unexpected type form (got -0x30)" | https://api.github.com/repos/WebAssembly/wabt/issues/2394/comments | 1 | 2024-02-19T06:51:37Z | 2024-02-19T09:41:33Z | https://github.com/WebAssembly/wabt/issues/2394 | 2,141,643,297 | 2,394 |
[
"WebAssembly",
"wabt"
] | The function prototype is available in the header file: `wasm-rt.h` line : 512
But is missing from the implementation file : `wasm-rt-impl.c`, it appears to have been removed here - 80b4f087aa65a7f23d3489f80eaa298a1cdb3913
Has it be deprecated? or has the function implementation been moved to another .c file? | WASM2C - What happened to wasm_rt_allocate_memory | https://api.github.com/repos/WebAssembly/wabt/issues/2391/comments | 3 | 2024-02-12T18:37:34Z | 2024-02-15T14:33:19Z | https://github.com/WebAssembly/wabt/issues/2391 | 2,130,730,550 | 2,391 |
[
"WebAssembly",
"wabt"
] | Given WASM
```wasm
0000024: 44 ; f64.const
0000025: 0000 0000 0000 e0c1 ; f64 literal
(module
(func (export "addTwo") (result f64)
f64.const -0x1p+31
)
)
```
and wasm2c conversion output
```c
//wasm2c test.wasm
f64 w2c__addTwo_0(w2c_* i... | [wasm2c] MSVC miscompiles for certain fp constants | https://api.github.com/repos/WebAssembly/wabt/issues/2388/comments | 6 | 2024-02-10T21:29:23Z | 2024-09-16T14:28:25Z | https://github.com/WebAssembly/wabt/issues/2388 | 2,128,719,817 | 2,388 |
[
"WebAssembly",
"wabt"
] | The decompiled output from wasm-decompile can be challenging to interpret since the function table is omitted from the resulting files. Annotating the function index within the output aids in comprehending which function is being invoked by the call_indirect instruction.
Consider the following WebAssembly text file, a... | Output results of the wasm-decompile to be easier to understand which function is called by call_indirect | https://api.github.com/repos/WebAssembly/wabt/issues/2384/comments | 1 | 2024-02-05T23:53:58Z | 2024-02-06T00:06:14Z | https://github.com/WebAssembly/wabt/issues/2384 | 2,119,679,400 | 2,384 |
[
"WebAssembly",
"wabt"
] | I am trying to use `call_ref` from [function references](https://webassembly.github.io/function-references/core/). According to the linked documentation, I thought that I should include a type index when using `call_ref` instruction. But `wat2wasm` does not build with a type index passed.
I tried with this example, ... | Use of call_ref does not take a type indice in wat2wasm | https://api.github.com/repos/WebAssembly/wabt/issues/2383/comments | 1 | 2024-02-04T18:26:20Z | 2024-02-06T01:17:51Z | https://github.com/WebAssembly/wabt/issues/2383 | 2,117,246,796 | 2,383 |
[
"WebAssembly",
"wabt"
] | Running `wat2wasm` on a rather big file with many nested if-statements segfaults.
Version: wabt 1.0.32-1 (debian bookworm)
System: Debian (with enough RAM + swap)
Steps to reproduce:
```
wasm2wat CertiCoq.Benchmarks.tests.color.wasm > color.wat // color.wat is ~20GB
wat2wasm color.wat -o color.wam ... | wat2wasm segfaults on .wat file with many nested if statements | https://api.github.com/repos/WebAssembly/wabt/issues/2377/comments | 9 | 2024-01-30T21:26:47Z | 2024-05-14T21:44:31Z | https://github.com/WebAssembly/wabt/issues/2377 | 2,108,812,790 | 2,377 |
[
"WebAssembly",
"wabt"
] | The example code doesn't compile with `wat2wasm`
https://github.com/WebAssembly/component-model/blob/main/design/mvp/Explainer.md#component-definitions
```wat
(component
(component
(core module (func (export "one") (result i32) (i32.const 1)))
(core module (func (export "two") (result f32) (f32.cons... | feature request: support for WASI preview 2 component model | https://api.github.com/repos/WebAssembly/wabt/issues/2376/comments | 1 | 2024-01-30T09:35:35Z | 2024-01-30T17:40:58Z | https://github.com/WebAssembly/wabt/issues/2376 | 2,107,359,733 | 2,376 |
[
"WebAssembly",
"wabt"
] | Fresh clone of WABT on macOS built with CMake and make results in wat2wasm reporting errors like this one:
`local build % ./wat2wasm ../third_party/testsuite/f32.wast -o ~/wasm_test.wasm
../third_party/testsuite/f32.wast:19:1: error: unexpected token (, expected EOF.
(assert_return (invoke "add" (f32.const -0x0p+0... | wat2wasm fails converting .wast files in testsuite: error: unexpected token (, expected EOF. | https://api.github.com/repos/WebAssembly/wabt/issues/2375/comments | 4 | 2024-01-29T14:53:51Z | 2024-01-29T16:18:01Z | https://github.com/WebAssembly/wabt/issues/2375 | 2,105,683,450 | 2,375 |
[
"WebAssembly",
"wabt"
] | is there a way to make wast2json ignore errors in binary modules? (`(module binary ...`)
i want to convert wast files from exception-handling proposal.
eg. https://github.com/WebAssembly/exception-handling/blob/123ac59cb650e9537ce129bb2977243bcbe9a773/test/core/try_table.wast
i know that wabt doesn't support the l... | can wast2json write out binary modules as they are without error checking? | https://api.github.com/repos/WebAssembly/wabt/issues/2374/comments | 4 | 2024-01-27T16:00:05Z | 2024-06-20T12:12:51Z | https://github.com/WebAssembly/wabt/issues/2374 | 2,103,646,022 | 2,374 |
[
"WebAssembly",
"wabt"
] | Assuming I’ve properly initialized each thread via `wasm_rt_init_thread()`, is it undefined behavior to instantiate a module in thread A and then call into the instance in threads B, C, D, *etc*.? We can assume only one thread ever calls into the instance at any time.
Based on some quick tests, this behavior appear... | wasm2c: Are module instances truly thread-safe? | https://api.github.com/repos/WebAssembly/wabt/issues/2372/comments | 5 | 2024-01-25T14:20:12Z | 2024-01-25T19:34:56Z | https://github.com/WebAssembly/wabt/issues/2372 | 2,100,501,693 | 2,372 |
[
"WebAssembly",
"wabt"
] | Hi 👋 and thanks for the great project!
For generating the tests of our [Java WASM interpreter](https://github.com/dylibso/chicory) we are relying heavily on `wast2json`, sadly there are no releases for Mac ARM, and people need to recompile this project locally to get a working version of the executable.
Do you ... | Mac ARM support | https://api.github.com/repos/WebAssembly/wabt/issues/2366/comments | 15 | 2024-01-12T15:36:26Z | 2024-03-26T15:17:10Z | https://github.com/WebAssembly/wabt/issues/2366 | 2,079,120,345 | 2,366 |
[
"WebAssembly",
"wabt"
] | In the test/dump/typed_func_refds_params ,
ref----0x6b,but in the wasmGC standard,ref----0x64.
if translat... | In the case of wasmGC, the encoding of the ref is incorrect. such as test/dump/typed_func_refds_params | https://api.github.com/repos/WebAssembly/wabt/issues/2364/comments | 0 | 2024-01-08T03:17:10Z | 2024-01-08T03:17:10Z | https://github.com/WebAssembly/wabt/issues/2364 | 2,069,542,322 | 2,364 |
[
"WebAssembly",
"wabt"
] | The function-references and gc proposals are going to be merged into the spec soon (as well as the "v4" revision of the exception-handling proposal, which we don't support yet). It could be good to talk about our plan for supporting these features in WABT. I think there's a few options to put on the table:
- We work... | Plan for GC and beyond | https://api.github.com/repos/WebAssembly/wabt/issues/2348/comments | 9 | 2023-12-05T02:03:52Z | 2024-03-28T21:33:34Z | https://github.com/WebAssembly/wabt/issues/2348 | 2,025,130,969 | 2,348 |
[
"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 | 3 | 2023-11-20T09:17:52Z | 2025-01-15T02:09:46Z | 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 | 2024-09-24T00:46:04Z | 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 | 2024-09-24T00:46:03Z | 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 |
Subsets and Splits
Unique Owner-Repo Count
Counts the number of unique owner-repos in the dataset, providing a basic understanding of diverse repositories.