| commit | ca85396d9990293c5456f7da5fc71cc5906eca0c | [log] [tgz] |
|---|---|---|
| author | bjacob <benoitjacob@google.com> | Thu Sep 22 15:50:40 2022 -0400 |
| committer | GitHub <noreply@github.com> | Thu Sep 22 15:50:40 2022 -0400 |
| tree | 1d514d86b6bca75237b56cb683b047654ff181f5 | |
| parent | 116db8778a4bbec72fedcdffccfa2c83ef7b4e1b [diff] |
Make iree-benchmark-suites buildable with some backends disabled. (#10508) Note: the reason why iree-test-deps wasn't failing similarly was that `iree_single_backend_generated_trace_runner_test` and `iree_check_single_backend_test_suite` were already performing a similar check, but they do it on the `DRIVER`, not on the `TARGET_BACKEND`. They can do so because these targets are built in the device build dir, where `IREE_HAL_DRIVER_*` variables are set and drivers are built, because drivers are part of the runtime, so they're built in the device build dir. Unlike those targets, `iree-benchmark-suites` is built in the host build dir, so we shouldn't enable or disable benchmarks based on `IREE_HAL_DRIVER_*` here. Instead, what is relevant (and to the point of fixing the module compile error that caused me to look into this) is a check on `IREE_TARGET_BACKEND_*`. Possibly these could be unified by switching also `iree-test-deps` to this `IREE_TARGET_BACKEND_*` check.
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.