Switch CMake to build libIREECompiler.so without explicit export lists. (#14357) The need to run generate_exports.py was always a hack that we didn't want to carry forward. This patch does the CMake plumbing needed to build the compiler shared library without such a workaround. It relies on the source level annotations to control what gets exported in deployment builds (in dev builds, everything is exported on Posix). This also adds a mechanism for super-projects to extend what gets exported (which was the motivating use case to fix this). There is a similar-effect (but different mechanism) way to achieve this on Bazel, but it requires a Bazel upgrade to use. I'll do that separately. Until then, the old export lists will be used for Bazel.
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.