commit | 0b0da79b6320b756b4ef70853a3623d43e560941 | [log] [tgz] |
---|---|---|
author | bjacob <benoitjacob@google.com> | Tue Jul 19 13:17:03 2022 -0400 |
committer | GitHub <noreply@github.com> | Tue Jul 19 13:17:03 2022 -0400 |
tree | 83e4483eab9195b5ef3e77d03a6b73e28770e262 | |
parent | 3b7e2746a26ae322e48ed44694df0b8c5ce59dc1 [diff] |
Comments and NFC tidying on atomics in synchronization.* (#9832) * Explain the weakly ordered atomics in iree_slim_mutex_t (now that I finally understand them and while I haven't forgotten) * NFC refactoring of iree_slim_mutex_{lock,trylock}: move the compare_exchange op to a shared helper. * Fix some atomic comments on iree_notification_t (an acq/rel operation is not quite the same as a barrier, the ordering relationship only applies on ops on the same object).
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.