You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Upgrade libm and make no-std config testable (#241)
* Make everything build and test without 'std' feature
Signed-off-by: Brian Anderson <andersrb@gmail.com>
* Use faster constructor in vec_bytebuf.
`vec![0; len]` uses a specialized intrinsic codepath, which, at least in debug
mode, is extremely faster than `resize`.
This makes the `alloc` test pass instantaneously instead of taking minutes.
Signed-off-by: Brian Anderson <andersrb@gmail.com>
* Fix a comment about core+mmap
Signed-off-by: Brian Anderson <andersrb@gmail.com>
* Don't use traits to call libm functions
These no longer exist in the latest revision of libm.
Signed-off-by: Brian Anderson <andersrb@gmail.com>
* Upgrade libm to 0.2.1
Fixes#240
Signed-off-by: Brian Anderson <andersrb@gmail.com>
* Remove warning from readme about debug-mode panics from libm
Signed-off-by: Brian Anderson <andersrb@gmail.com>
* Test no-std configuration under travis
Signed-off-by: Brian Anderson <andersrb@gmail.com>
* rustfmt
Signed-off-by: Brian Anderson <andersrb@gmail.com>
Copy file name to clipboardexpand all lines: README.md
-3
Original file line number
Diff line number
Diff line change
@@ -35,9 +35,6 @@ wasmi = {
35
35
36
36
When the `core` feature is enabled, code related to `std::error` is disabled.
37
37
38
-
Floating point operations in `no_std` use [`libm`](https://crates.io/crates/libm), which sometimes panics in debug mode (https://github.com/japaric/libm/issues/4).
39
-
So make sure to either use release builds or avoid WASM with floating point operations, for example by using [`deny_floating_point`](https://docs.rs/wasmi/0.4.0/wasmi/struct.Module.html#method.deny_floating_point).
40
-
41
38
# License
42
39
43
40
`wasmi` is primarily distributed under the terms of both the MIT
0 commit comments