commit | b8f0306f0f99b3636b604f423cccba0122a8c84e | [log] [tgz] |
---|---|---|
author | Scott Todd <scott.todd0@gmail.com> | Thu Aug 08 14:01:39 2024 -0700 |
committer | GitHub <noreply@github.com> | Thu Aug 08 14:01:39 2024 -0700 |
tree | 2d72dda1180be7f7b11b1d4307a323d8f38c732f | |
parent | 052c0004f9b15333679ce6bb63513e43819a18f2 [diff] |
Switch from build_runtime.sh to inlined CMake commands. (#18162) I'm trying to reduce the number of scripts that we have in [`build_tools/cmake/`](https://github.com/iree-org/iree/tree/main/build_tools/cmake), so changes like https://github.com/iree-org/iree/pull/17996 will be easier to make with confidence. This makes the `build_test_runtime` CI job no longer depend on these scripts: * [`build_tools/cmake/build_runtime.sh`](https://github.com/iree-org/iree/blob/main/build_tools/cmake/build_runtime.sh) * After this, the last use will be deleted in https://github.com/iree-org/iree/pull/18144 * [`build_tools/cmake/setup_build.sh`](https://github.com/iree-org/iree/blob/main/build_tools/cmake/setup_build.sh) * [`build_tools/cmake/setup_ccache.sh`](https://github.com/iree-org/iree/blob/main/build_tools/cmake/setup_ccache.sh) These layers of scripts made it somewhat easier to have CI workflows just run scripts, but the scripts grew branches over time that obscured what was actually running. In many cases the commands are quite simple and can just be inlined. Other ideas for simplification: * Use https://github.com/marketplace/actions/get-cmake to install Ninja across platforms (with caching) * Use https://github.com/marketplace/actions/run-cmake together with CMake presets ("configure"/"build"/"test", possibly also "workflow") * Reduce reliance on [`build_tools/cmake/ctest_all.sh`](https://github.com/iree-org/iree/blob/main/build_tools/cmake/ctest_all.sh) - that excludes some tests based on platform (e.g. Windows) and adds exclude labels for tests that need special hardware (e.g. GPUs), but ideally `ctest` would work out of the box without such a script ci-exactly: build_test_runtime
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
Package | Release status |
---|---|
GitHub release (stable) | |
GitHub release (nightly) | |
Python iree-compiler | |
Python iree-runtime |
Host platform | Build status |
---|---|
Linux | |
macOS | |
Windows |
For the full list of workflows see https://iree.dev/developers/general/github-actions/.
See our website for more information.
Community meeting recordings: IREE YouTube channel
IREE is licensed under the terms of the Apache 2.0 License with LLVM Exceptions. See LICENSE for more information.