| commit | be0f1e1da6db17b5308d34c0a1a248e3896a6ce0 | [log] [tgz] |
|---|---|---|
| author | Stella Laurenzo <laurenzo@google.com> | Mon Apr 03 13:34:38 2023 -0700 |
| committer | GitHub <noreply@github.com> | Mon Apr 03 13:34:38 2023 -0700 |
| tree | 3f09c0c91804459a1bd513d55a8b5faccde097c0 | |
| parent | d81e29b6993b63aed2421dfd5d2ed05663456d52 [diff] |
Roll-up of changes needed to support the nvgpu out of tree project. (#12888) * Adds CMake scoped IREE_PACKAGE_ROOT_DIR and IREE_PACKAGE_ROOT_PREFIX to replace hard-coded path to namespace logic in iree_package_ns (and uses within IREE/removes the special casing). * Adds support for `BAZEL_TO_CMAKE_PRESERVES_ALL_CONTENT_ABOVE_THIS_LINE ` to bazel_to_cmake. Been carrying this patch for a while and ended up needing it. * Further generalizes bazel_to_cmake target resolution so that it is customizable as needed out of tree. * Moves the `iree::runtime::src::defs` target to `iree::defs` and puts it in the right place in the tree to avoid special casing. * Ditto but for `iree::compiler::src::defs` * Adds a bit more logging to `_DEBUG_IREE_PACKAGE_NAME` mode. * Makes iree_tablegen_library consult a scoped `IREE_COMPILER_TABLEGEN_INCLUDE_DIRS` var for additional include directories (makes it possible to use out of tree). * Adds `NVPTXDesc` and `NVPTXInfo` targets to HAL_Target_CUDA. No idea why this was triggering for me but was getting undefined deps. Must have been coming in elsewhere in a more full featured build. * Fixes iree-opt initialization sequence with respect to command line options. Also fixed the test which should have been verifying this. * Fixed pytype issue in bazel_to_cmake that could theoretically happen. Fixes build issues related to the out of tree build for https://github.com/openxla/community/issues/71
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.