T0b1/wasmtime
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Update README

Browse Source
This commit is contained in:
Jef
2019-03-26 15:07:20 +01:00
parent cf9c57e279
commit 4f21ffc006
1 changed files with 2 additions and 94 deletions
Download Patch File Download Diff File Expand all files Collapse all files

96
README.md
View File

@@ -165,100 +165,8 @@ Now obviously I'm not advocating for replacing FireFox's optimising compiler wit
## Specification compliance
Currently 73 out of 74 of the spec suite tests pass when run in Wasmtime with Lightbeam as a backend. Here's the full test output:
```
running 74 tests
test spec_testsuite::binary ... ok
test spec_testsuite::align ... ok
test spec_testsuite::block ... ok
test spec_testsuite::br ... ok
test spec_testsuite::break_drop ... ok
test spec_testsuite::address ... ok
test spec_testsuite::br_if ... ok
test spec_testsuite::comments ... ok
test spec_testsuite::const_ ... ok
test spec_testsuite::call ... ok
test spec_testsuite::custom ... ok
test spec_testsuite::custom_section ... ok
test spec_testsuite::data ... ok
test spec_testsuite::conversions ... ok
test spec_testsuite::elem ... ok
test spec_testsuite::exports ... ok
test spec_testsuite::call_indirect ... ok
test spec_testsuite::endianness ... ok
test spec_testsuite::f32_bitwise ... ok
test spec_testsuite::f64 ... ok
test spec_testsuite::f32_cmp ... ok
test spec_testsuite::f32 ... ok
test spec_testsuite::fac ... ok
test spec_testsuite::br_table ... ok
test spec_testsuite::f64_bitwise ... ok
test spec_testsuite::float_memory ... ok
test spec_testsuite::float_literals ... ok
test spec_testsuite::forward ... ok
test spec_testsuite::f64_cmp ... ok
test spec_testsuite::float_misc ... ok
test spec_testsuite::func_ptrs ... ok
test spec_testsuite::get_local ... ok
test spec_testsuite::globals ... ok
test spec_testsuite::i32 ... ok
test spec_testsuite::func ... ok
test spec_testsuite::imports ... ok
test spec_testsuite::inline_module ... ok
test spec_testsuite::if_ ... ok
test spec_testsuite::i64 ... ok
test spec_testsuite::int_literals ... ok
test spec_testsuite::labels ... ok
test spec_testsuite::linking ... ok
test spec_testsuite::int_exprs ... ok
test spec_testsuite::loop_ ... ok
test spec_testsuite::left_to_right ... ok
test spec_testsuite::memory ... ok
test spec_testsuite::memory_redundancy ... ok
test spec_testsuite::float_exprs ... ok
test spec_testsuite::memory_grow ... ok
test spec_testsuite::memory_trap ... ok
test spec_testsuite::resizing ... ok
test spec_testsuite::return_minimal ... ok
test spec_testsuite::select ... ok
test spec_testsuite::nop ... ok
test spec_testsuite::return_ ... ok
test spec_testsuite::set_local ... ok
test spec_testsuite::stack ... ok
test spec_testsuite::store_retval ... ok
test spec_testsuite::start ... ok
test spec_testsuite::switch ... ok
test spec_testsuite::token ... ok
test spec_testsuite::traps ... ok
test spec_testsuite::type_ ... ok
test spec_testsuite::typecheck ... ok
test spec_testsuite::tee_local ... ok
test spec_testsuite::unreached_invalid ... ok
test spec_testsuite::unwind ... FAILED
test spec_testsuite::utf8_custom_section_id ... ok
test spec_testsuite::utf8_import_field ... ok
test spec_testsuite::utf8_import_module ... ok
test spec_testsuite::utf8_invalid_encoding ... ok
test spec_testsuite::skip_stack_guard_page ... ok
test spec_testsuite::unreachable ... ok
test spec_testsuite::names ... ok
failures:
---- spec_testsuite::unwind stdout ----
thread 'spec_testsuite::unwind' panicked at 'assertion failed: `(left == right)`
left: `Some(0..=1)`,
right: `None`', /home/jef/Documents/GitHub/Vurich/lightbeam/src/function_body.rs:323:29
note: Run with `RUST_BACKTRACE=1` environment variable to display a backtrace.
failures:
spec_testsuite::unwind
test result: FAILED. 73 passed; 1 failed; 0 ignored; 0 measured; 3 filtered out
```
Lightbeam passes 100% of the specification test suite, but that doesn't necessarily mean that it's 100% specification-compliant. Hopefully as we run a fuzzer against it we can find any issues and get Lightbeam to a state where it can be used in production.
## Getting involved
Our [issue tracker][issue tracker] is pretty barren right now since this is currently more-or-less a one-person project, but if you want to get involved jump into the [CraneStation Gitter room][cranestation-gitter] and someone can direct you to the right place. I wish I could say "the most useful thing you can do is play with it and open issues where you find problems" but until it passes the spec suite that won't be very helpful.