commit | 36f2451913c025c725f2d7e03935d2e9da9a872c | [log] [tgz] |
---|---|---|
author | Marius Brehler <marius.brehler@iml.fraunhofer.de> | Thu Aug 04 17:39:03 2022 +0200 |
committer | GitHub <noreply@github.com> | Thu Aug 04 08:39:03 2022 -0700 |
tree | de3539e95b7226ec597b190b856e253ae79d5425 | |
parent | a0943ed99ea31723b839a2234a3070f46d5f2bab [diff] |
Don't report compiler specifics if not built (#10002) With #9474 the compiler inputs and outputs are always reported even though the compiler might not be built (e.g. when only building the runtime). This can be confusing for example when using a snapshot install of the compiler that generates the workload (especially if it should generate a C source module) which is than cross-compiled together with the runtime (this the case in iree-bare-metal for example). With this patch inputs and outputs (non at all in the example given before) are only reported when building the compiler.
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.