commit | 3d5813e55619ab1c5b26e98e7bb4e8d7b6201e34 | [log] [tgz] |
---|---|---|
author | Scott Todd <scotttodd@google.com> | Tue Jun 29 16:37:46 2021 -0700 |
committer | GitHub <noreply@github.com> | Tue Jun 29 16:37:46 2021 -0700 |
tree | d6ffb695c2dc443860c1338417a7cbc565316995 | |
parent | c4a9f5d2c797b91b32b1661ecda39147f3fb84f1 [diff] | |
parent | 6989e2b8c9b779a92efeafed5ae88c93e6ffde7f [diff] |
Add Buildkite configs for tracing and runtime builds. (#6352) I see this "build configurations" pipeline growing to include other combinations of CMake options we want to test. This pipeline should be able to run on presubmit and mainly checks that configurations are valid and build successfully. I don't have the pipeline configured to run any tests or benchmarks. However, we _could_ set up a "minimum size" configuration and upload some metrics from that to our benchmarking infrastructure. Sample builds: * https://buildkite.com/iree/scotttodd-test-pipeline/builds/35 * https://buildkite.com/iree/scotttodd-test-pipeline/builds/37 Additional changes: * Allow building samples without the compiler (lets the runtime build work without disabling samples) * Add `CMAKE_DL_LIBS` to `iree::base::tracing` (fixes the tracing build on Linux) * Rework how options are tested in `iree/samples/simple_embedding/CMakeLists.txt` and how `IREE_HOST_BINARY_ROOT` is used in general. Now, regardless of cross compilation status, if `IREE_HOST_BINARY_ROOT` is set then it will be searched for tool executables. Runtime builds are responsible for ensuring that any host builds were completed using a set of target backends compatible with their HAL drivers (for example: a runtime build `-DIREE_HAL_DRIVERS_TO_BUILD=vmvx` attempting to use a host tools build with `-DIREE_TARGET_BACKENDS_TO_BUILD=vulkan-spirv` will likely fail).
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!
IREE is licensed under the terms of the Apache 2.0 License with LLVM Exceptions. See LICENSE for more information.