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))
diff --git a/build_tools/bazel/iree_check_test.bzl b/build_tools/bazel/iree_check_test.bzl
index a72fe41..67832e9 100644
--- a/build_tools/bazel/iree_check_test.bzl
+++ b/build_tools/bazel/iree_check_test.bzl
@@ -19,7 +19,7 @@
name,
src,
target_backend,
- driver,
+ driver = None,
compiler_flags = [],
runner_args = [],
opt_tool = "//iree/tools:iree-opt",
@@ -34,7 +34,9 @@
name: name of the generated test.
src: source mlir file containing the module.
target_backend: target backend to compile for.
- driver: driver to run the module with.
+ driver: driver to run the module with. This can be omitted to test only
+ compilation, but consider omiting the driver as a hacky abuse of the
+ rule since compilation on its own not use iree-check-module.
compiler_flags: additional flags to pass to the compiler. Bytecode translation and backend
flags are passed automatically.
runner_args: additional runner_args to pass to iree-check-module. The driver and input file
@@ -67,6 +69,9 @@
visibility = ["//visibility:private"],
)
+ if not driver:
+ return
+
native_test(
name = name,
args = [
@@ -84,7 +89,7 @@
name,
srcs,
target_backend,
- driver,
+ driver = None,
compiler_flags = [],
runner_args = [],
opt_tool = "//iree/tools:iree-opt",
@@ -101,7 +106,9 @@
name: name of the generated test suite.
srcs: source mlir files containing the module.
target_backend: target backend to compile for.
- driver: driver to run the module with.
+ driver: driver to run the module with. This can be omitted to test only
+ compilation, but consider omiting the driver as a hacky abuse of the
+ rule since compilation on its own not use iree-check-module.
compiler_flags: additional flags to pass to the compiler. Bytecode translation and backend
flags are passed automatically.
runner_args: additional runner_args to pass to the underlying iree-check-module tests. The
@@ -145,6 +152,10 @@
**kwargs
)
tests.append(test_name)
+
+ if not driver:
+ return
+
native.test_suite(
name = name,
tests = tests,
