commit | ad8f733a3db8d057d9a5ced0353fd09784ed909a | [log] [tgz] |
---|---|---|
author | Geoffrey Martin-Noble <gcmn@google.com> | Thu Oct 21 09:18:54 2021 -0700 |
committer | GitHub <noreply@github.com> | Thu Oct 21 09:18:54 2021 -0700 |
tree | c8ea7b404dc733ebfa54f7819c31b75aeefd8686 | |
parent | cde0270b213028070f5600bb6c294e9f400a0d9e [diff] |
Some cleanup to docker images (#7406) At this point all of our builds use Python. With https://github.com/google/iree/pull/7347 the last holdouts are growing a dep on yaml to be able to run traces. So I squashed `cmake-python` into `cmake` and shortened all the dependents by dropping `python` from their name. Some other cleanups, some of which were unfortunately necessary to be able to rebuild our images. Hooray unreproducible builds! 1. The rbe-toolchain image was never actually updated to bump the swiftshader commit in https://github.com/google/iree/pull/7117 and https://github.com/google/iree/pull/6859, and the newer commits don't actually build there so I had to restore the commit in the Dockerfile to the one that has actually always been the one the image is using. See https://github.com/google/iree/issues/7419. 2. The place we were fetching the Vulkan SDK from is no longer available, so I had to rebundle it and stash it in our GCS. Upgrading Vulkan is a huge undertaking that I'm not going to undertake right now. 3. Deleted the `cmake-bazel-frontends-android` image, which is unused.
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.