Gregory Sobol
25d6a49f1c
fmt
2022-10-05 18:42:38 +03:00
Gregory Sobol
7b49e4d6d6
fix popcnt for m1 and add test
2022-09-30 17:02:30 +03:00
Wolfgang Silbermayr
7df3e3ca23
Rename {native,typed} functions, reintroduce *_with_env variants
2022-08-05 14:27:44 +02:00
John Sharratt's Shared Account
5aa356f222
Fixed a memory corruption issue with JS memory operations that were reusing invalid views
2022-07-31 20:31:41 +10:00
Syrus Akbary
a419ccdf52
Move Webassembly objects to Store and remove Context
...
Co-authored-by: ptitSeb <sebastien.chev@gmail.com >
Co-authored-by: Manos Pitsidianakis <manos@wasmer.io >
2022-07-19 15:31:51 +03:00
ptitSeb
267a09ce8e
Migrate compiler tests to the new Context API
2022-07-19 15:31:51 +03:00
ptitSeb
0cd9dfe3e0
Fixed linter warnings/errors
2022-06-15 19:26:57 +03:00
Manos Pitsidianakis
8aa225a192
api/sys: Replace ImportObject with new type Imports
2022-06-08 14:09:40 +03:00
Manos Pitsidianakis
008c6720d7
tests/compilers/issues.rs: update broken Memory API usage
2022-06-08 14:09:40 +03:00
Simonas Kazlauskas
13a926adc6
regression test for GPR exhaustion during calls
2022-01-24 20:37:28 +02:00
Simonas Kazlauskas
6dc24623e3
Regression test for #2721
...
The wasm snippet in the test corresponds to roughly:
```rust
let name = "bananapeach";
banana(a, b, c, name.len() as _, name.as_ptr() as _, f, g, h);
```
however sometime between 2.0 and 2.1 the name pointer is no longer being
passed through as an argument. Instead a 0 gets passed in.
To make things weirder, if `name.as_ptr()` is passed through multiple
times, the second time the pointer will get passed correctly.
2021-12-14 14:44:51 +02:00
Syrus Akbary
e0fce0ae9d
Use test that trigger issue
2021-07-28 17:05:46 -07:00
Syrus Akbary
69cdfbb134
Added issues to test in compilers
2021-07-28 14:41:22 -07:00
