commit | 4d68d1e574138184b67041b30e234c1f8f7c1358 | [log] [tgz] |
---|---|---|
author | Ben Vanik <benvanik@google.com> | Tue Dec 14 13:23:00 2021 -0800 |
committer | Ben Vanik <benvanik@google.com> | Tue Jan 04 10:19:07 2022 -0800 |
tree | 5b4373b3145a655695f4bf4c324a9d2586c9c50a | |
parent | 3785011ee23af494c4c4d8a2d952637445139c10 [diff] |
Adding iree_hal_buffer_transfer_range. The existing methods for read/write/copy route to this more generic form and the existing mapping behavior is used as a default. Implementations can override this now if they need to perform special processing (like webgpu/metal, which can't map). For the existing implementations we'll likely want to switch to different primitives when it makes sense to avoid needing to allocate mappable memory.
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.