issue_owner_repo listlengths 2 2 | issue_body stringlengths 0 261k ⌀ | issue_title stringlengths 1 925 | issue_comments_url stringlengths 56 81 | issue_comments_count int64 0 2.5k | issue_created_at stringlengths 20 20 | issue_updated_at stringlengths 20 20 | issue_html_url stringlengths 37 62 | issue_github_id int64 387k 2.91B | issue_number int64 1 131k |
|---|---|---|---|---|---|---|---|---|---|
[
"WebAssembly",
"wabt"
] | in "expr-visitor.cc":
HandleDefaultState use a lot of "case":
Result ExprVisitor::HandleDefaultState(Expr* expr) {
switch (expr->type()) {
case ExprType::AtomicLoad:
CHECK_RESULT(delegate_->OnAtomicLoadExpr(cast<AtomicLoadExpr>(expr)));
break;
case ExprType::AtomicStore:
CHECK_RES... | use map and function pointer replace "case" | https://api.github.com/repos/WebAssembly/wabt/issues/1143/comments | 5 | 2019-08-14T09:43:55Z | 2019-08-28T03:17:24Z | https://github.com/WebAssembly/wabt/issues/1143 | 480,582,393 | 1,143 |
[
"WebAssembly",
"wabt"
] | While attempting to test the SIMD `v128.const` instruction, I ran into failures parsing certain wast files. The following commands fail:
```
wget https://raw.githubusercontent.com/WAVM/WAVM/master/Test/spec/simd/simd_const.wast
wast2json --enable-simd simd_const.wast -o simd_const.json
```
The returned errors ... | wast2json fails on float literals | https://api.github.com/repos/WebAssembly/wabt/issues/1139/comments | 2 | 2019-08-08T16:34:31Z | 2019-08-12T19:35:01Z | https://github.com/WebAssembly/wabt/issues/1139 | 478,576,266 | 1,139 |
[
"WebAssembly",
"wabt"
] | It seems to cause some confusion because it doesn't, for example, write out a symbols table.
See:
https://stackoverflow.com/questions/57294541/error-linking-wasm-object-files-with-wasm-ld/57367477#57367477
We could improve it but I'm not who this would benefit exactly. Do we have users for such a feature? | Improve `wat2wasm --relocatable` support (or remove it completely). | https://api.github.com/repos/WebAssembly/wabt/issues/1137/comments | 7 | 2019-08-06T00:30:45Z | 2022-05-19T01:50:21Z | https://github.com/WebAssembly/wabt/issues/1137 | 477,112,589 | 1,137 |
[
"WebAssembly",
"wabt"
] | I am not sure it is a bug, here is it:
```scheme
$ cat in.scm
(module
(func $start (result i32)
(i32.const 42)))
$ wat2wasm in.scm -o out.wasm
$ wasm2wat out.wasm -f --generate-names
(module
(type $t0 (func (result i32)))
(func $f0 (type $t0) (result i32)
(i32.const 42)))
```
The `star... | spurious type in wat2wasm then wasm2wat and loosing `$start` | https://api.github.com/repos/WebAssembly/wabt/issues/1135/comments | 1 | 2019-08-04T13:06:45Z | 2019-08-05T08:19:31Z | https://github.com/WebAssembly/wabt/issues/1135 | 476,551,660 | 1,135 |
[
"WebAssembly",
"wabt"
] | I was hoping to use `wasm2c` on some WebAssembly modules that use the multi-value extension, but I get
```
wasm2c currently support only default feature flags.
```
I know that you know about this, just opening this issue to track any possible implementation. | wasm2c --enable-multi-value | https://api.github.com/repos/WebAssembly/wabt/issues/1134/comments | 8 | 2019-08-02T09:30:59Z | 2022-04-01T06:56:58Z | https://github.com/WebAssembly/wabt/issues/1134 | 476,087,574 | 1,134 |
[
"WebAssembly",
"wabt"
] | As far as i can see, wat2wasm can only take a single WAT file as input. Are you aware of any tool that would take several wasm file as input (each of them being a module) and assemble them into a single wasm file ?
Or would concatenating all the wat files together before invoking wat2wasm do the trick ?
| Wat to Asm linker ? | https://api.github.com/repos/WebAssembly/wabt/issues/1133/comments | 8 | 2019-07-30T18:20:33Z | 2020-09-10T17:21:22Z | https://github.com/WebAssembly/wabt/issues/1133 | 474,736,895 | 1,133 |
[
"WebAssembly",
"wabt"
] | In the JavaScript, you can use the `WebAssembly.instantiate` function to load a WASM file and use the various methods provided by the WASM file. I want to know if there is such a way in C++ that I can use WASM files directly.
| How to call a native webassembly file in c/c++ source code? | https://api.github.com/repos/WebAssembly/wabt/issues/1130/comments | 5 | 2019-07-25T09:39:21Z | 2019-09-25T20:23:41Z | https://github.com/WebAssembly/wabt/issues/1130 | 472,765,699 | 1,130 |
[
"WebAssembly",
"wabt"
] | HI all,
I'm currently writing wat code and using wat2wasm to compile wat source code to wasm binary format. I was wondering if there is a way to tell wasm-interp to use the original source names when tracing the execution (--trace option). I initially though the --debug-names option in wat2 wasm would serve that pur... | Source names in wasm-interp --trace | https://api.github.com/repos/WebAssembly/wabt/issues/1127/comments | 1 | 2019-07-23T18:58:33Z | 2022-05-19T01:43:50Z | https://github.com/WebAssembly/wabt/issues/1127 | 471,875,188 | 1,127 |
[
"WebAssembly",
"wabt"
] | I am working on a branch of https://github.com/google/schism that uses reference types. To check that my .wasm is fine, I used wasm2wat from today; however it crashes:
```
wingo@milano:~/src/schism$ ~/src/wabt/out/gcc/Debug/wasm2wat --enable-reference-types schism-stage0.wasm
terminate called after throwing an in... | Crash disassembling file built with reference types | https://api.github.com/repos/WebAssembly/wabt/issues/1124/comments | 3 | 2019-07-22T13:30:39Z | 2019-07-22T19:00:03Z | https://github.com/WebAssembly/wabt/issues/1124 | 471,096,789 | 1,124 |
[
"WebAssembly",
"wabt"
] | ### Vulnerability/issue
A crash takes place at `error-formatter.cc` which is not caught.
### Steps to reproduce the behavior
PoC: [poc.zip](https://github.com/WebAssembly/wabt/files/3409440/poc.zip)
Run: `wat2wasm poc`
Crash:
```
terminate called after throwing an instance of 'std::length_error'
what(): ... | Exception handling issue in error-formatter.cc | https://api.github.com/repos/WebAssembly/wabt/issues/1120/comments | 0 | 2019-07-19T04:38:05Z | 2019-07-19T18:21:48Z | https://github.com/WebAssembly/wabt/issues/1120 | 470,133,688 | 1,120 |
[
"WebAssembly",
"wabt"
] | ### Vulnerability/issue
Assertion failed in wabt::WastLexer::IsCharClass()
### Steps to reproduce the behavior
PoC: [poc.zip](https://github.com/WebAssembly/wabt/files/3408735/poc.zip)
Run: ```wat2wasm poc ```
### Crash
```
wat2wasm: wabt/src/wast-lexer.cc:390: static bool wabt::WastLexer::IsCharClass(int... | Assertion failed in wabt::WastLexer::IsCharClass() in wast-lexer.cc | https://api.github.com/repos/WebAssembly/wabt/issues/1117/comments | 1 | 2019-07-18T23:36:03Z | 2019-07-19T03:16:37Z | https://github.com/WebAssembly/wabt/issues/1117 | 470,045,451 | 1,117 |
[
"WebAssembly",
"wabt"
] | See https://github.com/WebAssembly/wabt/pull/1111#issuecomment-511921663. It's not clear to me why, but 32-bit MSVC still doesn't produce the right values for two of the tests in `conversions.wast`:
```
(assert_return (invoke "f32.convert_i64_u" (i64.const 0x8000008000000001)) (f32.const 0x1.000002p+63))
(assert_r... | f32.convert_i64_u on MSVC 32-bit | https://api.github.com/repos/WebAssembly/wabt/issues/1113/comments | 1 | 2019-07-16T22:01:15Z | 2019-07-19T01:08:40Z | https://github.com/WebAssembly/wabt/issues/1113 | 468,886,298 | 1,113 |
[
"WebAssembly",
"wabt"
] | ### Environment
| Questions | Answers
|----------------------|--------------------
| Related Binary | wasm-interp
| Commit | commit 41adcbfb106e035f90de93d472c10461bf4f3f9c
### Vulnerability/issue
Assertion failed in wabt::interp::Executor::CopyResults() in interp.cc
### S... | [wasm-interp] Assertion failed in wabt::interp::Executor::CopyResults() in interp.cc | https://api.github.com/repos/WebAssembly/wabt/issues/1108/comments | 1 | 2019-07-11T08:54:38Z | 2019-07-15T23:26:36Z | https://github.com/WebAssembly/wabt/issues/1108 | 466,756,342 | 1,108 |
[
"WebAssembly",
"wabt"
] | Hi all,
I looks like the wat2wasm tool doesn't support bytes expressed in hexadecimal as stated by the WASM 1.0 spec.
Concretely wat2wasm is fine with :
`(data 0 (i32.const 4) "\04\00\00\00")`
but throw an error with:
`(data 0 (i32.const 4) 0x04 0x00 0x00 0x00)`
Is it a known problem with wat2 wasm or... | data segment byte coding not following spec ? | https://api.github.com/repos/WebAssembly/wabt/issues/1107/comments | 2 | 2019-07-10T14:08:23Z | 2019-07-10T14:23:28Z | https://github.com/WebAssembly/wabt/issues/1107 | 466,331,668 | 1,107 |
[
"WebAssembly",
"wabt"
] | ```
bin/wasm2c --version
unknown option '--version'
```
How can I do that? If it doesn't exist yet then:
**feature request:** allow me to ask the binary about its version number.
(obviously, `--version` for all of them: `bin/spectest-interp bin/wasm2c bin/wasm2wat bin/wasm-interp bin/wasm-objdump bin/w... | bin/wasm2c --version # how to ? | https://api.github.com/repos/WebAssembly/wabt/issues/1106/comments | 2 | 2019-07-08T22:47:37Z | 2019-10-21T20:35:27Z | https://github.com/WebAssembly/wabt/issues/1106 | 465,491,916 | 1,106 |
[
"WebAssembly",
"wabt"
] | Example test case from the spec test suite ([const.wast#L147](https://github.com/WebAssembly/testsuite/blob/master/const.wast#L147)):
```wasm
(module
(func
(f32.const nan:0x7f_ffff)
drop
)
)
```
According to the [specification](https://webassembly.github.io/spec/core/text/values.html#... | wat2wasm: float nan hex literals with underscores are reported as invalid | https://api.github.com/repos/WebAssembly/wabt/issues/1104/comments | 2 | 2019-07-03T15:03:11Z | 2019-07-29T21:53:11Z | https://github.com/WebAssembly/wabt/issues/1104 | 463,805,037 | 1,104 |
[
"WebAssembly",
"wabt"
] | `gtest` and `ply `seem to be packaged by Arch and Alpine (and presumably other distros, though perhaps not all). Is it necessary have them vendored as submodules?
It seems desirable for packaging to either not provide a vendored version, or have an option to use the system version instead. | Allow building with system gtest and ply | https://api.github.com/repos/WebAssembly/wabt/issues/1103/comments | 2 | 2019-07-02T03:42:01Z | 2019-07-16T00:59:07Z | https://github.com/WebAssembly/wabt/issues/1103 | 463,004,700 | 1,103 |
[
"WebAssembly",
"wabt"
] | Hello,
This is more probably an error on my part than an "issue", I'm just not sure where to get help on this...
Running Ubuntu, juste after "sudo apt install cmake", then "cmake .." (in the newly created build directory, as instructed). I get this
```
-- The C compiler identification is GNU 8.3.0
-- The CXX... | No CMAKE_CXX_COMPILER could be found | https://api.github.com/repos/WebAssembly/wabt/issues/1102/comments | 2 | 2019-06-29T19:16:13Z | 2019-07-02T23:00:51Z | https://github.com/WebAssembly/wabt/issues/1102 | 462,332,957 | 1,102 |
[
"WebAssembly",
"wabt"
] | I think it's a validation error in references types validation
| table.grow [i32, anyref] instead of [anyref, i32] | https://api.github.com/repos/WebAssembly/wabt/issues/1098/comments | 9 | 2019-06-27T10:41:58Z | 2019-07-29T21:55:39Z | https://github.com/WebAssembly/wabt/issues/1098 | 461,455,273 | 1,098 |
[
"WebAssembly",
"wabt"
] | I have a wasm .so with the following sections:
```
~/wabt/bin/wasm-objdump -h /home/keno/julia-wasm/julia/build-wasm/usr/lib/libjulia.so
libjulia.so: file format wasm 0x1
023d986: warning: unable to read u32 leb128: index
Sections:
Type start=0x0000000b end=0x000001cf (size=0x000001c4) count: 63
Im... | Add filtering by custom section name to wasm-objdump | https://api.github.com/repos/WebAssembly/wabt/issues/1095/comments | 4 | 2019-06-23T22:31:30Z | 2019-06-27T17:18:06Z | https://github.com/WebAssembly/wabt/issues/1095 | 459,625,434 | 1,095 |
[
"WebAssembly",
"wabt"
] | The `-ttf` option to `wasm-opt` stands for "translate to fuzz" and essentially makes wasm-opt into a test case generator for fuzzing.
However, it generates imports that `wasm-interp` doesn't know about, but are morally equivalent to `host.print` AFAICT:
```wasm
(import "fuzzing-support" "log-i32" (func $log-i32... | wasm-interp: support running wasm binaries created by `wasm-opt -ttf`? | https://api.github.com/repos/WebAssembly/wabt/issues/1094/comments | 2 | 2019-06-20T23:20:42Z | 2019-06-28T22:45:50Z | https://github.com/WebAssembly/wabt/issues/1094 | 458,930,644 | 1,094 |
[
"WebAssembly",
"wabt"
] | Hello, I am writing a homemade 3rd party interpreter, and wonder how to use test suite in `/test` to test my own one, instead of copying and renaming my executable to `wasm-interp` and move to `wabt/bin`. | Test suite supporting 3rd party interpreters? | https://api.github.com/repos/WebAssembly/wabt/issues/1093/comments | 4 | 2019-06-18T00:53:42Z | 2019-06-19T21:41:11Z | https://github.com/WebAssembly/wabt/issues/1093 | 457,209,805 | 1,093 |
[
"WebAssembly",
"wabt"
] | ### Environment
| Questions | Answers
|----------------------|--------------------
| Related Binary | wasm-interp
| Commit | commit 986f5cc8bb85ba4ecc0dd3ed82fa39565ce9c419
### Vulnerability/issue
Assertion failed in wabt::BinaryReaderInterp::EndElemSegmentInitExpr() in binar... | [wasm-interp] Assertion failed in wabt::BinaryReaderInterp::EndElemSegmentInitExpr() in binary-reader-interp.cc | https://api.github.com/repos/WebAssembly/wabt/issues/1091/comments | 0 | 2019-06-06T20:03:45Z | 2019-06-07T22:34:54Z | https://github.com/WebAssembly/wabt/issues/1091 | 453,214,126 | 1,091 |
[
"WebAssembly",
"wabt"
] | ### Environment
| Questions | Answers
|----------------------|--------------------
| Related Binary | wasm-interp
| Commit | commit 986f5cc8bb85ba4ecc0dd3ed82fa39565ce9c419
### Vulnerability/issue
Assertion failed in wabt::BinaryReaderInterp::OnDataSegmentData() in binary-rea... | [wasm-interp] Assertion failed in wabt::BinaryReaderInterp::OnDataSegmentData() in binary-reader-interp.cc | https://api.github.com/repos/WebAssembly/wabt/issues/1090/comments | 0 | 2019-06-06T20:01:43Z | 2019-06-07T22:35:00Z | https://github.com/WebAssembly/wabt/issues/1090 | 453,213,280 | 1,090 |
[
"WebAssembly",
"wabt"
] | ### Environment
| Questions | Answers
|----------------------|--------------------
| Related Binary | wasm-interp
| Commit | commit 986f5cc8bb85ba4ecc0dd3ed82fa39565ce9c419
### Vulnerability/issue
Assertion failed in wabt::TypeChecker::GetLabel() in type-checker.cc
### Ste... | [wasm-interp] Assertion failed in wabt::TypeChecker::GetLabel() in type-checker.cc | https://api.github.com/repos/WebAssembly/wabt/issues/1089/comments | 0 | 2019-06-06T19:59:16Z | 2019-06-07T22:34:33Z | https://github.com/WebAssembly/wabt/issues/1089 | 453,212,290 | 1,089 |
[
"WebAssembly",
"wabt"
] | Unicode symbols are currently mangled by the `wast2json` tool, which I noticed when trying to write a program that consumes and runs the JSON output.
For example, The `names.wast` file from the spec includes [a test case that uses a byte-order marker as a symbol](https://github.com/WebAssembly/spec/blob/master/test/... | wast2json double-encodes UTF-8 symbols | https://api.github.com/repos/WebAssembly/wabt/issues/1086/comments | 2 | 2019-05-28T22:55:40Z | 2019-06-07T16:53:50Z | https://github.com/WebAssembly/wabt/issues/1086 | 449,513,032 | 1,086 |
[
"WebAssembly",
"wabt"
] | I'm trying to compile for Windows using MinGW. I'm getting the following:
`error: #error unknown compiler`
This is the cmake command I'm running from the build directory:
`cmake --build . --config RELEASE --target install`
I'm getting a bunch of other errors too. Here is the whole command line output:
```
... | Can't compile for Windows | https://api.github.com/repos/WebAssembly/wabt/issues/1085/comments | 1 | 2019-05-21T02:15:44Z | 2022-05-19T01:43:35Z | https://github.com/WebAssembly/wabt/issues/1085 | 446,385,236 | 1,085 |
[
"WebAssembly",
"wabt"
] | See #1078. Example:
```
test.wast:1:17: error: invalid literal "11111111111"
(func i32.const 11111111111 drop)
^^^^^^^^^^^
```
Something like "literal out of range ..." would be a clearer message here. | Better error on literal overflow | https://api.github.com/repos/WebAssembly/wabt/issues/1080/comments | 0 | 2019-05-15T15:44:10Z | 2020-03-20T20:29:08Z | https://github.com/WebAssembly/wabt/issues/1080 | 444,512,429 | 1,080 |
[
"WebAssembly",
"wabt"
] | Hi,
Help needed, today I test for a max value literal of the ``f64`` number, and have error reports when convert wast to wasm binary:
```
literal.wast:42:47: error: invalid literal "1.79769313486232e+308"
(global $Double.MaxValue (mut f64) (f64.const 1.79769313486232e+308))
... | [Help] How to literal a very large number? | https://api.github.com/repos/WebAssembly/wabt/issues/1078/comments | 4 | 2019-05-11T05:39:23Z | 2019-05-15T15:44:32Z | https://github.com/WebAssembly/wabt/issues/1078 | 442,956,762 | 1,078 |
[
"WebAssembly",
"wabt"
] | hello,
I'm doing AFL fuzzy of "wasm-interp" program of WABT, latest master branch.
The attached binary file can crash ""wasm-interp", probably due to empty function body.
Just decompress the zip file and run command "wasm-interp fuzzy.wasm" to reproduce it.
[fuzzy.zip](https://github.com/WebAssembly/wabt/files/... | malformed binary WASM file crashes "wasm-interp" | https://api.github.com/repos/WebAssembly/wabt/issues/1077/comments | 2 | 2019-05-08T15:30:52Z | 2019-05-09T00:59:09Z | https://github.com/WebAssembly/wabt/issues/1077 | 441,796,450 | 1,077 |
[
"WebAssembly",
"wabt"
] | ### Input file
`hello_world.wat`
```wasm
(module
(func $output_println (import "System::Output" "println") (param i32))
(func $factorial (param $n i32) (result i32)
(if
(i32.eq
(get_local $n)
(i32.const 1)
)
(then
... | wat2wasm - type mismatch in implicit return | https://api.github.com/repos/WebAssembly/wabt/issues/1075/comments | 4 | 2019-05-05T23:05:09Z | 2019-05-16T00:17:25Z | https://github.com/WebAssembly/wabt/issues/1075 | 440,500,996 | 1,075 |
[
"WebAssembly",
"wabt"
] | https://webassembly.github.io/wabt/demo/wat2wasm/
selecting factorial, an error shows
```
Error: resolveNames failed:
test.wast:13:12: error: undefined function variable "$fac"
call $fac
^^^^
```
Was reading this https://developer.mozilla.org/en-US/docs/WebAssembly/Understanding_the_text_... | Factorial Example doesn't work | https://api.github.com/repos/WebAssembly/wabt/issues/1072/comments | 1 | 2019-04-27T08:50:06Z | 2019-04-29T01:01:57Z | https://github.com/WebAssembly/wabt/issues/1072 | 437,922,548 | 1,072 |
[
"WebAssembly",
"wabt"
] | These seems to be new. Wondering if its a known is issue?
```
ninja: Entering directory `out/clang/Debug/'
[48/94] Building CXX object CMakeFiles/wabt.dir/src/interp/interp-trace.cc.o
../../../src/interp/interp-trace.cc:35:11: warning: enumeration value 'RefFunc' not handled in switch [-Wswitch]
switch (opco... | New -Wswitch warnings | https://api.github.com/repos/WebAssembly/wabt/issues/1070/comments | 1 | 2019-04-24T01:06:32Z | 2019-04-24T07:24:41Z | https://github.com/WebAssembly/wabt/issues/1070 | 436,451,869 | 1,070 |
[
"WebAssembly",
"wabt"
] | Hi,
Help needed, when i use wat2wasm for compile ``S-Expression`` text format script to WebAssembly binary, error reports:
```
base64.wast:252:22: error: type mismatch in if true branch, expected [] but got [i32]
(call $array_push (get_local $chars) (call $fromCharCode ...
... | [Bugs Report] failed to compile | https://api.github.com/repos/WebAssembly/wabt/issues/1067/comments | 4 | 2019-04-20T10:04:27Z | 2019-04-21T09:07:12Z | https://github.com/WebAssembly/wabt/issues/1067 | 435,380,140 | 1,067 |
[
"WebAssembly",
"wabt"
] | It seems the `section_starts_` is shared for all custom sections, so it ends up being overwritten if there are multiple custom sections in the binary. It probably should be changed to use the section index instead of the section code. @sbc100 | [wasm-objdump] File offset for relocation of custom sections is wrong | https://api.github.com/repos/WebAssembly/wabt/issues/1064/comments | 0 | 2019-04-15T18:58:52Z | 2019-04-15T18:58:52Z | https://github.com/WebAssembly/wabt/issues/1064 | 433,431,000 | 1,064 |
[
"WebAssembly",
"wabt"
] | Running the 1.0.10 testsuite (test/run-tests.py) on big-endian arches (POWER8/ppc64 and s390x) yields the following failed tests:
```
- test/binary/bad-call-indirect-reserved.txt
- test/binary/bad-data-count-mismatch.txt
- test/binary/bad-data-count-order-after-code.txt
- test/binary/bad-data-count-order-before-... | 247 test failures on big-endian arches (ppc64 and s390x) | https://api.github.com/repos/WebAssembly/wabt/issues/1063/comments | 6 | 2019-04-15T14:12:19Z | 2021-02-03T10:55:06Z | https://github.com/WebAssembly/wabt/issues/1063 | 433,305,063 | 1,063 |
[
"WebAssembly",
"wabt"
] | Hi,
I followed the instruction on your github and did a
cmake ..
I got no error, but in the clang/Debug there is no binary file wat2wasm etc...
Where will the binaries reside after building using cmake ?
Regards
Ranga | cmake error no wat2wasm binary found | https://api.github.com/repos/WebAssembly/wabt/issues/1062/comments | 2 | 2019-04-11T06:08:52Z | 2019-04-12T07:05:08Z | https://github.com/WebAssembly/wabt/issues/1062 | 431,845,624 | 1,062 |
[
"WebAssembly",
"wabt"
] | Hi there!
I found that the result of wasm2wat is not real s-expression, the "if-else" branching code is an indentation-based syntax just like Python. This inconsistency makes it harder to use Lisp-like languages (for example, Scheme) to implement a static analyzer. It means people have to write a specific parser for i... | The result of wasm2wat is not real s-expression | https://api.github.com/repos/WebAssembly/wabt/issues/1048/comments | 4 | 2019-03-20T12:45:02Z | 2019-03-22T12:32:29Z | https://github.com/WebAssembly/wabt/issues/1048 | 423,231,662 | 1,048 |
[
"WebAssembly",
"wabt"
] | When building 1.0.10 on Fedora rawhide (development) with gcc-9.0.1 and RHEL/CentOS 7 with gcc-4.8.5, the following tests fail on POWER8 (ppc64le) architecture:
```
- test/spec/conversions.txt
expected error code 0, got 2.
STDOUT MISMATCH:
--- expected
+++ actual
@@ -1 +1,3 @@
-401/401 tests passed.... | test failures on POWER8 (ppc64le) | https://api.github.com/repos/WebAssembly/wabt/issues/1045/comments | 11 | 2019-03-15T19:13:40Z | 2025-03-04T22:59:46Z | https://github.com/WebAssembly/wabt/issues/1045 | 421,667,429 | 1,045 |
[
"WebAssembly",
"wabt"
] | Running the 1.0.10 testsuite (`test/run-tests.py`) on x86 32bit (i686) yields the following failed tests:
```
- test/interp/unary.txt
STDOUT MISMATCH:
--- expected
+++ actual
@@ -21,7 +21,7 @@
f64_abs() => f64:100.000000
f64_sqrt_neg_is_nan() => i32:1
f64_sqrt_100() => f64:10.000000
-f64_ce... | test failures on x86 32bit (i686) | https://api.github.com/repos/WebAssembly/wabt/issues/1044/comments | 26 | 2019-03-15T15:38:56Z | 2025-03-04T18:47:36Z | https://github.com/WebAssembly/wabt/issues/1044 | 421,580,529 | 1,044 |
[
"WebAssembly",
"wabt"
] | Running the testsuite from 1.0.10 on ARM (armv7hl and aarch64) and POWER8 (ppc64le) fails:
```
- test/interp/simd-unary.txt
STDOUT MISMATCH:
--- expected
+++ actual
@@ -25,8 +25,8 @@
f32x4_abs_0() => v128:0x00000000 0x7fc00000 0x449a5000 0x3f800000
f64x2_abs_0() => v128:0x00000000 0x00000000 0x000... | test/interp/simd-unary.txt fails on ARM and POWER8 | https://api.github.com/repos/WebAssembly/wabt/issues/1043/comments | 3 | 2019-03-15T13:25:04Z | 2019-04-15T18:01:09Z | https://github.com/WebAssembly/wabt/issues/1043 | 421,517,384 | 1,043 |
[
"WebAssembly",
"wabt"
] | When configuring the build (1.0.10) with cmake 2.8, I get the following error:
```
-- Using prebuilt re2c lexer
CMake Error at CMakeLists.txt:281 (cmake_parse_arguments):
Unknown CMake command "cmake_parse_arguments".
Call Stack (most recent call first):
CMakeLists.txt:311 (wabt_executable)
-- Configuring in... | Unknown CMake command "cmake_parse_arguments" with cmake 2.8 | https://api.github.com/repos/WebAssembly/wabt/issues/1042/comments | 2 | 2019-03-15T10:52:42Z | 2019-09-12T08:46:49Z | https://github.com/WebAssembly/wabt/issues/1042 | 421,460,505 | 1,042 |
[
"WebAssembly",
"wabt"
] | how to run wabt VM in intel SGX | how to run wabt VM in intel SGX | https://api.github.com/repos/WebAssembly/wabt/issues/1040/comments | 2 | 2019-03-09T20:41:50Z | 2019-03-18T07:07:37Z | https://github.com/WebAssembly/wabt/issues/1040 | 419,113,426 | 1,040 |
[
"WebAssembly",
"wabt"
] | Due to the way my WASM code is generated, I have code bodies that explicitly list 0 locals of a certain type. It seems the binary reader (intentionally) fails on this:
error: local count must be > 0
Is there a reason why this restriction is there? I couldn't immediately find something in the spec that constra... | Binary reader errors on local count > 0 | https://api.github.com/repos/WebAssembly/wabt/issues/1038/comments | 1 | 2019-03-08T20:38:15Z | 2019-03-18T19:36:39Z | https://github.com/WebAssembly/wabt/issues/1038 | 418,948,712 | 1,038 |
[
"WebAssembly",
"wabt"
] | I saw parser tests allow `--enable-reference-types` but current version of wat2wasm it seems not support this flag?
Also this missing in [online version](https://webassembly.github.io/wabt/demo/wat2wasm/) | wat2wasm with reference types | https://api.github.com/repos/WebAssembly/wabt/issues/1035/comments | 3 | 2019-03-06T11:27:10Z | 2019-03-07T09:05:18Z | https://github.com/WebAssembly/wabt/issues/1035 | 417,755,734 | 1,035 |
[
"WebAssembly",
"wabt"
] | The command line tools behave differently than the [web demos](https://webassembly.github.io/wabt/demo/) because the demos haven't been updated with the great renaming https://github.com/WebAssembly/wabt/pull/985
| libwabt.js on gh-pages branch needs updating | https://api.github.com/repos/WebAssembly/wabt/issues/1024/comments | 1 | 2019-02-21T19:09:44Z | 2019-02-21T19:23:28Z | https://github.com/WebAssembly/wabt/issues/1024 | 413,079,453 | 1,024 |
[
"WebAssembly",
"wabt"
] | At the https://github.com/WebAssembly/wabt/blob/master/src/wabt.post.js#L151 it uses "Pointer_stringify" function, which has been deprecated. See https://github.com/emscripten-core/emscripten/pull/8011
This prevents using the wabt demo with newly built libwabt.js. Thanks!
| Deprecated function Pointer_stringify used | https://api.github.com/repos/WebAssembly/wabt/issues/1020/comments | 1 | 2019-02-19T22:28:23Z | 2019-02-20T00:40:51Z | https://github.com/WebAssembly/wabt/issues/1020 | 412,154,519 | 1,020 |
[
"WebAssembly",
"wabt"
] | Edit: solution presented here is incorrect. In some cases the relocation offset is wrong, but not all.
When using the following code with `wat2wasm`:
```
(module
(type $t0 (func (param i32) (param i32) (param i32) (param i32) (param i32) (param i32) ))
(type $t1 (func (result i32)))
(type $t2 (fu... | Relocations seem to be off by 2 | https://api.github.com/repos/WebAssembly/wabt/issues/1018/comments | 2 | 2019-02-19T07:43:18Z | 2019-02-19T11:41:16Z | https://github.com/WebAssembly/wabt/issues/1018 | 411,787,008 | 1,018 |
[
"WebAssembly",
"wabt"
] | The real objcopy is the ultimate swiss army knife tool and we don't want to emulate all of its feature but we we probably want to be able to such as
- Extracting/dumping selected section(s)
- Replacing sections
- Stripping sections
See `objcopy` options: `--remove-section`, `--add-section`, `--update-section`,... | Create `wasm-objcopy` tool for manipulating wasm binary files | https://api.github.com/repos/WebAssembly/wabt/issues/1015/comments | 2 | 2019-02-12T18:51:25Z | 2025-02-11T17:53:55Z | https://github.com/WebAssembly/wabt/issues/1015 | 409,448,329 | 1,015 |
[
"WebAssembly",
"wabt"
] | The [dylink section](https://github.com/WebAssembly/tool-conventions/blob/master/DynamicLinking.md) says
> The "dylink" section should be the very first section in the module; this allows detection of whether a binary is a dynamic library without having to scan the entire contents.
It looks like wabt does not pre... | Order of dylink section? | https://api.github.com/repos/WebAssembly/wabt/issues/1011/comments | 1 | 2019-02-11T18:26:05Z | 2019-02-11T19:28:57Z | https://github.com/WebAssembly/wabt/issues/1011 | 408,915,440 | 1,011 |
[
"WebAssembly",
"wabt"
] | When I run `wasm-opt -O3 myfile.wasm`, I get no error and no output, but `myfile.wasm` stays the same. This lead me to believe that these files had already been properly optimized.
Then @kripken told me that I had to specify an output file like this: `wasm-opt -O3 -o myfile2.wasm myfile.wasm`.
I think a no-op lik... | `wasm-opt -O <file>` should throw an error | https://api.github.com/repos/WebAssembly/wabt/issues/1008/comments | 2 | 2019-02-08T20:05:51Z | 2019-02-08T21:44:59Z | https://github.com/WebAssembly/wabt/issues/1008 | 408,304,556 | 1,008 |
[
"WebAssembly",
"wabt"
] | Instead it looks like it supports and old version of the proposal based on a custom section.
This makes it hard when working with llvm output which uses the latest spec proposal (i.e. a new known section '13').
I started down the road of converting it but god pretty bogged down
| wabt does not support the new binary format for exceptions | https://api.github.com/repos/WebAssembly/wabt/issues/1006/comments | 2 | 2019-02-06T22:56:56Z | 2019-03-09T01:05:19Z | https://github.com/WebAssembly/wabt/issues/1006 | 407,469,589 | 1,006 |
[
"WebAssembly",
"wabt"
] | We discovered that the `wast2json` and `spectest-interp` tools in this repository were perfect for our use case of trying to execute wasm spec tests, as they did all the heavy lifting of figuring out what to do where! (and made it so we didn't have to write a wast parser)
We noticed, however, that we mistakenly thou... | Exit code of spectest-interp | https://api.github.com/repos/WebAssembly/wabt/issues/1002/comments | 3 | 2019-02-01T21:48:14Z | 2019-02-02T18:12:11Z | https://github.com/WebAssembly/wabt/issues/1002 | 405,886,554 | 1,002 |
[
"WebAssembly",
"wabt"
] | Would it be possible to include sha256 files for the Windows zip files? Specifically, this would make it easier to integrate with the [Scoop](https://github.com/lukesampson/scoop) package manager. | sha256 files for Windows releases? | https://api.github.com/repos/WebAssembly/wabt/issues/995/comments | 2 | 2019-01-16T07:38:14Z | 2019-01-16T16:27:25Z | https://github.com/WebAssembly/wabt/issues/995 | 399,682,696 | 995 |
[
"WebAssembly",
"wabt"
] | ke .. | https://api.github.com/repos/WebAssembly/wabt/issues/994/comments | 0 | 2019-01-11T14:32:28Z | 2019-01-16T05:56:16Z | https://github.com/WebAssembly/wabt/issues/994 | 398,312,756 | 994 | |
[
"WebAssembly",
"wabt"
] | Update: In another place in the docs, it says to manually create a "build" folder and run "cmake .." from there. This seems to work. I did not keep track of where I found "cmake ." in the toplevel folder, unfortunately.
Bottom line:
* The manual specifies multiple "recipes" for building wabt which work or don't wor... | Build broken on Mac OS X | https://api.github.com/repos/WebAssembly/wabt/issues/992/comments | 4 | 2018-12-31T12:13:25Z | 2022-04-27T18:02:31Z | https://github.com/WebAssembly/wabt/issues/992 | 394,972,062 | 992 |
[
"WebAssembly",
"wabt"
] | Debug build, just updated the sources (but crashed with older code too). Fedora 28, compiled with clang 6.0.1, it looks like.
Test file mytest.wat:
(module (func (export "fn")))
Run thusly:
wat2wasm -d mytest.wat
Backtrace:
```
#0 wabt::Stream::WriteData (this=0x0, src=0x7fffffffd230, size=9, desc=0x0,
... | wat2wasm segfaults with -d | https://api.github.com/repos/WebAssembly/wabt/issues/989/comments | 2 | 2018-12-20T13:45:03Z | 2018-12-25T18:37:36Z | https://github.com/WebAssembly/wabt/issues/989 | 393,052,800 | 989 |
[
"WebAssembly",
"wabt"
] | failed to compile, because the output binary `wasm2c`, conflicts with the existing directory of the same name | failed to compile | https://api.github.com/repos/WebAssembly/wabt/issues/988/comments | 1 | 2018-12-20T02:20:50Z | 2022-04-27T18:02:59Z | https://github.com/WebAssembly/wabt/issues/988 | 392,859,135 | 988 |
[
"WebAssembly",
"wabt"
] | - the output.c via `wasm2c` fails to compile, if the .wasm was produced by Emscripten, due to missing defines, e.g.
```
/* import: 'env' 'enlargeMemory' */
extern u32 (*Z_envZ_enlargeMemoryZ_iv)(void) = &enlargeMemory;
/* import: 'env' 'getTotalMemory' */
extern u32 (*Z_envZ_getTotalMemoryZ_iv)(void) = &getTotalMe... | the output.c via `wasm2c` fails to compile | https://api.github.com/repos/WebAssembly/wabt/issues/987/comments | 4 | 2018-12-20T02:20:11Z | 2022-02-22T15:51:42Z | https://github.com/WebAssembly/wabt/issues/987 | 392,859,006 | 987 |
[
"WebAssembly",
"wabt"
] | The test fails on OpenBSD:
```
- test/wasm2c/spec/names.txt
expected error code 0, got 1.
STDERR MISMATCH:
--- expected
+++ actual
@@ -0,0 +1,22 @@
+Error running "cc -c -o /tmp/wabt/out/test/wasm2c/spec/names/names.2.o names.2.c -I/tmp/wabt/wasm2c -DWASM_RT_MODULE_PREFIX=Z_names_2":
+names.2.c... | Test that we can use some libc hidden names without conflict. | https://api.github.com/repos/WebAssembly/wabt/issues/981/comments | 2 | 2018-12-17T10:39:03Z | 2022-02-22T15:50:45Z | https://github.com/WebAssembly/wabt/issues/981 | 391,651,170 | 981 |
[
"WebAssembly",
"wabt"
] | When building [wasmtime](https://github.com/CraneStation/wasmtime), which uses wabt via [wabt Rust bindings](https://crates.io/crates/wabt-sys), on MSVC in Appveyor, I see warnings like this:
```
C:\Users\appveyor\.cargo\registry\src\github.com-1ecc6299db9ec823\wabt-sys-0.5.2\wabt\src/string-view.h(165): warning C... | noexcept warning, treated as error on MSVC in Appveyor | https://api.github.com/repos/WebAssembly/wabt/issues/980/comments | 2 | 2018-12-17T08:31:29Z | 2019-01-16T05:57:49Z | https://github.com/WebAssembly/wabt/issues/980 | 391,604,828 | 980 |
[
"WebAssembly",
"wabt"
] | I want to use the parameter --enable-reference-types from #938 with libwabt.js like in #920.
Please can you add support for it. | How to pass --enable-reference-types to libwabt.js? | https://api.github.com/repos/WebAssembly/wabt/issues/978/comments | 2 | 2018-12-16T10:17:04Z | 2019-03-18T19:37:40Z | https://github.com/WebAssembly/wabt/issues/978 | 391,452,997 | 978 |
[
"WebAssembly",
"wabt"
] | Consider this module:
```wasm
(module
(func $dup (result i32 i32)
(i32.const 0)
(i32.const 0)
)
(func $foo (result i32)
(call $dup)
(drop))
)
```
Note that `$dup` returns two arguments, but only one of them is consumed by `(drop)`. Yet `wasm2wat` produces this output with `--fold-exprs... | wasm2wat --fold-expr confused by multi-return | https://api.github.com/repos/WebAssembly/wabt/issues/977/comments | 4 | 2018-12-15T00:10:48Z | 2018-12-18T18:07:33Z | https://github.com/WebAssembly/wabt/issues/977 | 391,319,857 | 977 |
[
"WebAssembly",
"wabt"
] | I found this while using another project that depends on `wabt`. I could not build the project on windows. I narrowed the issue down to `wabt`. I may not understand something about building `wabt` on windows (which is very likely). It appears to fail on linking a static library.
Dev environment:
Windows 10
Git Bas... | Cannot build project with wabt on windows | https://api.github.com/repos/WebAssembly/wabt/issues/972/comments | 3 | 2018-12-09T08:28:39Z | 2018-12-10T18:13:29Z | https://github.com/WebAssembly/wabt/issues/972 | 388,999,391 | 972 |
[
"WebAssembly",
"wabt"
] | If I provide a module name, eg. `(module $foo)` in the [wat2wasm demo](https://webassembly.github.io/wabt/demo/wat2wasm/index.html), I see the custom "name" section in the build log.
However, if I run `wat2wasm` on the same source and then do `wasm-objdump --details` on the binary it produces, the "name" section isn... | Different behavior when using wat2wasm online demo vs local binary | https://api.github.com/repos/WebAssembly/wabt/issues/967/comments | 4 | 2018-12-03T22:52:13Z | 2018-12-04T19:56:46Z | https://github.com/WebAssembly/wabt/issues/967 | 387,041,585 | 967 |
[
"WebAssembly",
"wabt"
] | If I try to convert from wasm to wat and back to wasm again, like this:
```
$ wasm2wat foo.wasm > foo.wat
$ wat2wasm foo.wat > foo2.wasm
```
I get errors saying: `error: redefinition of local "$my_local"`
@nomeata pointed out to me that:
> The names for locals are not unique (and need not be, [per spec]... | error: redefinition of local "$my_local" | https://api.github.com/repos/WebAssembly/wabt/issues/966/comments | 2 | 2018-12-03T18:37:37Z | 2018-12-04T18:08:38Z | https://github.com/WebAssembly/wabt/issues/966 | 386,949,975 | 966 |
[
"WebAssembly",
"wabt"
] | I'm trying to create a module which I'm intending to compile in into my program. The module looks like the following:
```WebAssembly
(module
(import "env" "__stack_pointer" (global $sp (mut i32)))
(func (export "reserve_stack") (param $size i32)
get_global $sp
get_local $size
... | Creating wasm object file with wat2wasm | https://api.github.com/repos/WebAssembly/wabt/issues/965/comments | 8 | 2018-11-30T15:35:47Z | 2018-12-03T15:47:15Z | https://github.com/WebAssembly/wabt/issues/965 | 386,236,638 | 965 |
[
"WebAssembly",
"wabt"
] | ```
$ /dev/wasm/wabt/bin/wasm-objdump -d -x /tmp
terminate called after throwing an instance of 'std::bad_alloc'
what(): std::bad_alloc
Aborted
``` | wasm-objdump aborts if passed a directory name | https://api.github.com/repos/WebAssembly/wabt/issues/962/comments | 0 | 2018-11-29T20:09:03Z | 2019-01-16T05:57:59Z | https://github.com/WebAssembly/wabt/issues/962 | 385,905,998 | 962 |
[
"WebAssembly",
"wabt"
] | I run my code the code gives me some binary or supported txt format file. How can I get `.wasm` file from that?
Here is the some part of file (since file is too long can't upload full file)
```
ELF>P@8A@8 @ @@@��888 ȐȐ 0�0�"0�"��O ����"��"��TTTDDP�td�>�>�>TTQ�tdR�t... | How to get .wasm file from unsupported text file? | https://api.github.com/repos/WebAssembly/wabt/issues/961/comments | 3 | 2018-11-29T07:59:37Z | 2022-05-19T01:41:35Z | https://github.com/WebAssembly/wabt/issues/961 | 385,612,157 | 961 |
[
"WebAssembly",
"wabt"
] | Doing a git clone followed by 'make' results in:
```
Scanning dependencies of target wabt-unittests
[ 53%] Building CXX object CMakeFiles/wabt-unittests.dir/src/test-binary-reader.cc.o
In file included from /home/gback/emsdk/wabt/src/test-binary-reader.cc:17:
In file included from /home/gback/emsdk/wabt/third_pa... | fails to build on Ubuntu 18.04 | https://api.github.com/repos/WebAssembly/wabt/issues/951/comments | 4 | 2018-11-06T15:51:38Z | 2018-11-07T01:53:59Z | https://github.com/WebAssembly/wabt/issues/951 | 377,909,487 | 951 |
[
"WebAssembly",
"wabt"
] | According to the "Memory Instructions of WebAssembly Core Specification"
https://webassembly.github.io/spec/core/bikeshed/index.html#syntax-instr-memory
linear memory in wasm will access with load or store.
loads and stores are followed by the encoding of their memory-immediate {align:u32, offset:u32}
however, ... | did Thread::ReadMemory have implicit bugs? | https://api.github.com/repos/WebAssembly/wabt/issues/944/comments | 3 | 2018-11-02T11:12:01Z | 2018-11-08T04:54:18Z | https://github.com/WebAssembly/wabt/issues/944 | 376,767,720 | 944 |
[
"WebAssembly",
"wabt"
] | I have spent some time using wasm-interp to investigate some issues in compiled wasm code and think that It would be better to change the trace formatting scheme. In particular, I suggest to use `$` only for representing local variables of functions. I understand the current rule of `$` using but traces traces like thi... | Improvement of the interpretator traces | https://api.github.com/repos/WebAssembly/wabt/issues/943/comments | 4 | 2018-11-01T21:20:05Z | 2023-03-15T06:30:48Z | https://github.com/WebAssembly/wabt/issues/943 | 376,575,424 | 943 |
[
"WebAssembly",
"wabt"
] | See, for example [here](https://travis-ci.org/WebAssembly/wabt/jobs/447926261)
```
WARNING:root:not all asm.js optimizations are possible with ALLOW_MEMORY_GROWTH, disabling those. [-Walmost-asm]
ERROR:root:undefined exported function: "_dummy_workaround_for_emscripten_issue_7073"
CMakeFiles/libwabtjs.dir/build.m... | Fix emscripten error in Travis | https://api.github.com/repos/WebAssembly/wabt/issues/939/comments | 0 | 2018-10-30T17:18:10Z | 2018-11-01T17:28:13Z | https://github.com/WebAssembly/wabt/issues/939 | 375,603,333 | 939 |
[
"WebAssembly",
"wabt"
] | While I was testing my own webassembly compiler against the official interpreter tests, I was trying to verify the results against wabt, but accidentally discovered that the wat compiler fails part of `call_indirect.wast`. Namely, it is not verifying that the inline type declarations match the explicit type reference. ... | Fails to warn about malformed wat | https://api.github.com/repos/WebAssembly/wabt/issues/936/comments | 1 | 2018-10-25T19:20:23Z | 2018-10-30T19:58:24Z | https://github.com/WebAssembly/wabt/issues/936 | 374,094,454 | 936 |
[
"WebAssembly",
"wabt"
] | See https://github.com/WebAssembly/spec/issues/884
There are plans to rename many instructions, and we should implement them here. We'll want to keep support for the old names for a while, and we may even want to have a flag to output the old names too during the transition.
The full rename list is duplicated her... | Rename instructions in text format | https://api.github.com/repos/WebAssembly/wabt/issues/933/comments | 2 | 2018-10-16T18:27:14Z | 2019-01-16T05:58:26Z | https://github.com/WebAssembly/wabt/issues/933 | 370,741,035 | 933 |
[
"WebAssembly",
"wabt"
] | @aardappel mentioned that it would be nice to have a checklist when adding a new instruction; there are a lot of places that you need to change, and it's easy to miss some.
The compiler will catch a number of them, since adding a new enum to the opcodes list will create a warning, but there are some that only get fl... | Add checklist for new instructions | https://api.github.com/repos/WebAssembly/wabt/issues/932/comments | 1 | 2018-10-15T23:08:26Z | 2018-10-16T05:39:21Z | https://github.com/WebAssembly/wabt/issues/932 | 370,377,631 | 932 |
[
"WebAssembly",
"wabt"
] | We'll want the full suite of tests that wabt typically provides:
* `test/binary`
* `test/dump`
* `test/parse/expr`
* `test/typecheck`
We'll also want to run spec tests for the proposal (see `update-spec-tests.py`) | More tests for the tail-call feature | https://api.github.com/repos/WebAssembly/wabt/issues/929/comments | 0 | 2018-10-12T21:20:01Z | 2018-10-17T00:00:26Z | https://github.com/WebAssembly/wabt/issues/929 | 369,714,314 | 929 |
[
"WebAssembly",
"wabt"
] | First added in https://github.com/WebAssembly/wabt/pull/927 the bulk memory operations aren't fully validated yet. Right now they don't verify that the immediate indexes passed to `{table,memory}.{init,drop}` are valid segments for the table/memory sections. For validation to be complete we'll need to validate that the... | Implement further segment validation checks for bulk memory operations | https://api.github.com/repos/WebAssembly/wabt/issues/928/comments | 3 | 2018-10-12T20:12:51Z | 2020-03-20T20:36:31Z | https://github.com/WebAssembly/wabt/issues/928 | 369,694,988 | 928 |
[
"WebAssembly",
"wabt"
] | Rawgit is shutting down, see https://rawgit.com/ | Remove uses of rawgit | https://api.github.com/repos/WebAssembly/wabt/issues/924/comments | 0 | 2018-10-09T16:04:44Z | 2018-10-12T03:04:14Z | https://github.com/WebAssembly/wabt/issues/924 | 368,285,524 | 924 |
[
"WebAssembly",
"wabt"
] | ```
>cmake .. -DCMAKE_BUILD_TYPE=DEBUG -DCMAKE_INSTALL_PREFIX=.\bin -G "Visual Studio 15 2017 Win64"
CMake Error: Could not create named generator Visual Studio 15 2017 Win64
Generators
Visual Studio 14 2015 [arch] = Generates Visual Studio 2015 project files.
Optional [arch] c... | CMake build doesn't support Visual Studio 2017 | https://api.github.com/repos/WebAssembly/wabt/issues/923/comments | 2 | 2018-10-06T14:35:03Z | 2018-10-08T02:16:49Z | https://github.com/WebAssembly/wabt/issues/923 | 367,462,482 | 923 |
[
"WebAssembly",
"wabt"
] | I want to set the flag "--enable-saturating-float-to-int" to libwabt.js bevor calling parseWat() How can I do this? | How to pass parameters to libwabt.js? | https://api.github.com/repos/WebAssembly/wabt/issues/920/comments | 2 | 2018-10-03T20:52:14Z | 2018-10-07T14:19:03Z | https://github.com/WebAssembly/wabt/issues/920 | 366,523,405 | 920 |
[
"WebAssembly",
"wabt"
] | I have a .wasm file which has lots of mangled functions[which I Knew after converting it into .txt file using wasm-dis.ex]. How can I know the size of each function? Do we have any tool which can help me to achieve this? | Do we have any tool which can give me size of functions which are in .wasm file | https://api.github.com/repos/WebAssembly/wabt/issues/917/comments | 5 | 2018-10-01T12:15:17Z | 2019-01-16T06:03:47Z | https://github.com/WebAssembly/wabt/issues/917 | 365,433,512 | 917 |
[
"WebAssembly",
"wabt"
] | Somehow, a module in text format like
```wat
(module
(type $t0 (func (param i32)))
(type $t1 (func))
(import "env" "log" (func $log (type $t0)))
(func $main (type $t1)
block $B0
block $B1
br $B1
i32.const 3
call $log
end
i32.const 2
call $log
... | Issue with br labels in the JS build | https://api.github.com/repos/WebAssembly/wabt/issues/915/comments | 3 | 2018-09-23T23:07:08Z | 2018-09-24T00:51:48Z | https://github.com/WebAssembly/wabt/issues/915 | 362,985,834 | 915 |
[
"WebAssembly",
"wabt"
] | We still use asm.js for the emscripten version of wabt, but we should we use wasm instead. :-) | Convert online demo to wasm instead of asm.js | https://api.github.com/repos/WebAssembly/wabt/issues/914/comments | 0 | 2018-09-14T22:43:46Z | 2020-03-20T20:33:58Z | https://github.com/WebAssembly/wabt/issues/914 | 360,476,047 | 914 |
[
"WebAssembly",
"wabt"
] | I attempted to upload a .wasm to the [web demo](https://cdn.rawgit.com/WebAssembly/wabt/aae5a4b7/demo/wasm2wat/)
and it generated the following error:
<img width="1011" alt="image" src="https://user-images.githubusercontent.com/675259/45258041-aa58d600-b37e-11e8-8316-4a339d9fb889.png">
Just wondering if there's ... | web demo fails when trying to upload .wasm | https://api.github.com/repos/WebAssembly/wabt/issues/908/comments | 4 | 2018-09-08T19:58:06Z | 2018-09-11T00:18:23Z | https://github.com/WebAssembly/wabt/issues/908 | 358,323,682 | 908 |
[
"WebAssembly",
"wabt"
] | I'm getting this error when calling `.toText()` on any wasm module:
```
> new WabtModule().readWasm(buffer, {}).toText({})
libwabt.js:90376 Uncaught TypeError: Module._wabt_write_text_module is not a function
at eval (eval at <anonymous> (libwabt.js:90375), <anonymous>:1:1)
at WasmModule.toText (libwab... | libwabt.js: Module._wabt_write_text_module is not a function | https://api.github.com/repos/WebAssembly/wabt/issues/904/comments | 0 | 2018-08-30T00:47:20Z | 2018-09-13T07:06:18Z | https://github.com/WebAssembly/wabt/issues/904 | 355,383,206 | 904 |
[
"WebAssembly",
"wabt"
] | Referring to https://github.com/WebAssembly/wabt/issues/308#issuecomment-280735411, has there been recommended way for getting (walking) though the parsed result? And what would be the best entry point to wrap in order to use the tool in other languages such as Java?
| Using wabt tools as a parser | https://api.github.com/repos/WebAssembly/wabt/issues/897/comments | 3 | 2018-08-17T14:41:23Z | 2019-01-16T06:07:03Z | https://github.com/WebAssembly/wabt/issues/897 | 351,621,611 | 897 |
[
"WebAssembly",
"wabt"
] | This buggy (the global is not not marked as `mut`) wasm program
```
(module
(type $foo.ty (func))
(global $g i32 (i32.const -1))
(func $foo (type $foo.ty)
(set_global $g (i32.const 1))
)
(export "foo" (func $foo))
)
```
compiles to `.wasm`, and that files, passes the `wasm-validat... | Writing to non-mutable global variables passes validator | https://api.github.com/repos/WebAssembly/wabt/issues/894/comments | 2 | 2018-08-15T17:53:11Z | 2020-03-20T20:34:32Z | https://github.com/WebAssembly/wabt/issues/894 | 350,903,619 | 894 |
[
"WebAssembly",
"wabt"
] | Current version of Google test is using non-standard namespace that is not supported in Visual Studio 2017: google/googletest#1111
Would it be possible to update gtest to newer version? Its current head seems to work without changes to WABT code. | third_party/gtest fails to build with Visual Studio | https://api.github.com/repos/WebAssembly/wabt/issues/892/comments | 0 | 2018-08-14T20:39:45Z | 2018-08-15T21:27:42Z | https://github.com/WebAssembly/wabt/issues/892 | 350,589,070 | 892 |
[
"WebAssembly",
"wabt"
] | I'm currently looking at the short "stuff" example code that the wat2wasm demo website includes, and unless I'm mistaken its invalid?
It defines the start function as idx 1, but in the generated wasm that has the type 1, which is `[] -> [f32]` | Example "stuff" in wat2wasm demo is invalid or has conversion bug | https://api.github.com/repos/WebAssembly/wabt/issues/885/comments | 6 | 2018-08-03T12:19:04Z | 2018-08-03T18:15:45Z | https://github.com/WebAssembly/wabt/issues/885 | 347,374,540 | 885 |
[
"WebAssembly",
"wabt"
] | When executing [this](https://github.com/andoma/vmir/blob/master/examples/prebuilt/sha1sum.wasm) wasm file from the [vmir](https://github.com/andoma/vmir) project, `wasm-interp` fails with:
```
error: unknown import module "env"
000003b: error: OnImportFunc callback failed
```
I'm using [this](https://aur.arch... | error: OnImportFunc callback failed | https://api.github.com/repos/WebAssembly/wabt/issues/883/comments | 1 | 2018-08-01T11:14:52Z | 2022-05-19T01:38:13Z | https://github.com/WebAssembly/wabt/issues/883 | 346,555,758 | 883 |
[
"WebAssembly",
"wabt"
] | I'm not great at reading this kind of formal grammar but it looks like I should be able to write this according to the docs here https://webassembly.github.io/spec/core/text/values.html#strings:
```
(module
(memory (import "js" "mem") 1)
(data (i32.const 0) 123))
)
```
However I get the error:
```... | Integer values not allowed in data section | https://api.github.com/repos/WebAssembly/wabt/issues/881/comments | 1 | 2018-07-26T07:17:36Z | 2019-12-19T10:04:40Z | https://github.com/WebAssembly/wabt/issues/881 | 344,723,225 | 881 |
[
"WebAssembly",
"wabt"
] | Can we have binary releases please?
I'am totaly not into C and I don't even have the required build toolchain installed. Furthermore I do use Windows7. I really would appreciate if you could provide ready to go binaries. I don't know too much about what wabt does, but I need to use it as a build tool chain for anot... | Binary Releases | https://api.github.com/repos/WebAssembly/wabt/issues/875/comments | 1 | 2018-07-18T22:56:02Z | 2018-07-24T20:41:32Z | https://github.com/WebAssembly/wabt/issues/875 | 342,520,052 | 875 |
[
"WebAssembly",
"wabt"
] | I have been unable to find (or guess) how to declare a mutable global variable. Is it really supported? If so, what is the syntax?
Apologies in advance if this is a dense question.
FWIW I could find no examples of syntax for global variables (not imported) at all. I finally guessed it. This works for me.
... | Mutable global variables | https://api.github.com/repos/WebAssembly/wabt/issues/874/comments | 2 | 2018-07-15T03:14:08Z | 2018-07-18T16:23:11Z | https://github.com/WebAssembly/wabt/issues/874 | 341,288,294 | 874 |
[
"WebAssembly",
"wabt"
] | <pre>
options:
-h, --headers Print headers
-j, --section=SECTION Select just one section
-s, --full-contents Print raw section contents
-d, --disassemble Disassemble function bodies
--debug Print extra debug information
-x, --details ... | The option -h of wasm-objdump is ambiguous | https://api.github.com/repos/WebAssembly/wabt/issues/872/comments | 6 | 2018-07-14T11:42:45Z | 2018-08-03T04:05:15Z | https://github.com/WebAssembly/wabt/issues/872 | 341,230,463 | 872 |
[
"WebAssembly",
"wabt"
] | wat2wasm doesn't support Unicode names
According to the spec, we should support UTF-8-encoded names:
https://webassembly.github.io/spec/core/syntax/values.html#names
https://webassembly.github.io/spec/core/text/values.html#names
https://webassembly.github.io/spec/core/binary/values.html#names | wat2wasm doesn't support Unicode names | https://api.github.com/repos/WebAssembly/wabt/issues/871/comments | 2 | 2018-07-05T06:17:15Z | 2018-07-05T06:47:49Z | https://github.com/WebAssembly/wabt/issues/871 | 338,439,273 | 871 |
[
"WebAssembly",
"wabt"
] | error:
`CMake Warning at CMakeLists.txt:151 (message):
Error running file on dummy executable`
commond:
`cmake .. -DCMAKE_BUILD_TYPE=DEBUG -DCMAKE_INSTALL_PREFIX=..\bin -G "MinGW Makefiles"`
why? | cmake error | https://api.github.com/repos/WebAssembly/wabt/issues/870/comments | 7 | 2018-06-27T04:02:15Z | 2020-09-03T16:38:06Z | https://github.com/WebAssembly/wabt/issues/870 | 336,069,543 | 870 |
[
"WebAssembly",
"wabt"
] | I believe this: https://github.com/WebAssembly/wabt/blob/master/wasm2c/wasm-rt-impl.c#L106 is missing ` * PAGE_SIZE` and should read `memory->data = realloc(memory->data, new_pages * PAGE_SIZE);` | missing PAGE_SIZE | https://api.github.com/repos/WebAssembly/wabt/issues/868/comments | 1 | 2018-06-25T21:40:19Z | 2018-09-13T07:08:11Z | https://github.com/WebAssembly/wabt/issues/868 | 335,578,091 | 868 |
[
"WebAssembly",
"wabt"
] | https://github.com/WebAssembly/wabt/blob/b83e670d5287856d02377609d1ce11a66640f7f9/src/binary-reader-logging.cc#L514
Shouldn't the call to OnGlobalSymbol() at line 514 actually read OnFunctionSymbol()? | Call to wrong delegate function? | https://api.github.com/repos/WebAssembly/wabt/issues/866/comments | 1 | 2018-06-25T18:10:26Z | 2018-06-25T21:49:41Z | https://github.com/WebAssembly/wabt/issues/866 | 335,512,212 | 866 |
[
"WebAssembly",
"wabt"
] | Build fails on OpenBSD (and other BSDs) because of the check for alloca.
| error no alloca | https://api.github.com/repos/WebAssembly/wabt/issues/864/comments | 0 | 2018-06-18T11:43:42Z | 2018-06-18T18:06:00Z | https://github.com/WebAssembly/wabt/issues/864 | 333,235,321 | 864 |
Subsets and Splits
Unique Owner-Repo Count
Counts the number of unique owner-repos in the dataset, providing a basic understanding of diverse repositories.