commit | 0a561cdbcae0c47f05873cc88b8fb5fd43fe3187 | [log] [tgz] |
---|---|---|
author | Scott Todd <scotttodd@google.com> | Mon Mar 14 09:55:30 2022 -0700 |
committer | GitHub <noreply@github.com> | Mon Mar 14 09:55:30 2022 -0700 |
tree | e308afb166d69c25c7ed8fdf891f03d80165e99b | |
parent | 45bce4068608f047a4a1c8878828ff7d4f7331a5 [diff] |
Add a suite of tests for WebAssembly compilation. (#8516) This adds a new test suite to `iree/test/e2e/xla_ops` that uses IREE's WebAssembly target via `-iree-hal-target-backends=dylib-llvm-aot -iree-llvm-target-triple=wasm32-unknown-emscripten` (I'd use `llvm` as the target name, but our infra is hardcoded to the dylib name). Since we don't have a native WebAssembly HAL driver yet and the browser WebAssembly use is still experimental (and in no way integrated into our common build/test infra), these new "tests" are _just_ `iree_bytecode_module` targets that run at build time. The new tests don't actually use the check framework for "e2e" execution testing. Reusing the existing infra in this hacky way seems easiest to maintain and gives us a nice transition to enabling execution testing once a native Wasm HAL driver is added. I'd like to add similar coverage for other in-development compiler configurations (WebGPU) and expand to include more test suites (`test/e2e/tosa_ops/`, [google/iree-samples /tflitehub](https://github.com/google/iree-samples/tree/main/tflitehub), etc.). (there was some discussion about how to add this test coverage [on Discord here](https://discord.com/channels/689900678990135345/782059441641881630/951179647691919360))
IREE (Intermediate Representation Execution Environment, pronounced as “eerie”) is an MLIR-based end-to-end compiler and runtime that lowers Machine Learning (ML) models to a unified IR that scales up to meet the needs of the datacenter and down to satisfy the constraints and special considerations of mobile and edge deployments.
See our website for project details, user guides, and instructions on building from source.
IREE is still in its early phase. We have settled down on the overarching infrastructure and are actively improving various software components as well as project logistics. It is still quite far from ready for everyday use and is made available without any support at the moment. With that said, we welcome any kind of feedback on any communication channels!
See our website for more information.
IREE is licensed under the terms of the Apache 2.0 License with LLVM Exceptions. See LICENSE for more information.