commit | e18c45c3715f5dc5f04ea4e58936c74b81780a36 | [log] [tgz] |
---|---|---|
author | Scott Todd <scotttodd@google.com> | Thu Jan 06 08:41:18 2022 -0800 |
committer | GitHub <noreply@github.com> | Thu Jan 06 08:41:18 2022 -0800 |
tree | 637f140a85b98c6d63605b82752abb8181a43d51 | |
parent | 8199f3b3218a931cd0a165440b0d99472f4697a4 [diff] |
Add HAL CTS tests using executables. (#7982) Fixes https://github.com/google/iree/issues/5678 (for `executable_cache_test`, tests issuing dispatches can follow on later) Tests are filtered based on the HAL driver and compiler target being enabled as well as the presence of a new `COMPILER_TARGET_BACKEND` parameter to the `iree_hal_cts_test_suite()` function. If all of those conditions are met, executable testdata is generated using the new `-iree-mlir-to-hal-executable` translation mode and relevant tests in the suite get to load and reference the generated data. --- Rough edges: * ~~`iree_file_toc_t` definition copy/paste from `generate_embed_data` (since leaf binaries provide their own implementations)~~ * Specifying executable formats in CMake is hacky (`"\"embedded-elf-\" IREE_ARCH"`) * We may also want to test the system loader as well as the embedded loader, which is possible with another `iree_hal_cts_test_suite()` call I was also expecting the CMake to be a bit gnarly, and it is. Could maybe refactor into some helper functions or golf on the logic a bit. The interface to each HAL implementation is pretty nice, but the new implicit dependency on `iree-translate` makes it harder to use with out-of-tree runtime HAL drivers + compiler targets. Could pass `TRANSLATE_TOOL` as well 🤔
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.