commit | 784db04adc74c5bfa5a434f1e686a0ff69906e8b | [log] [tgz] |
---|---|---|
author | Ben Vanik <ben.vanik@gmail.com> | Sat Feb 25 11:10:21 2023 -0800 |
committer | Ben Vanik <ben.vanik@gmail.com> | Fri Mar 03 19:36:06 2023 -0800 |
tree | 8b77b8a12f7b52142885dbed3f9becde3b625f91 | |
parent | 91e73d39692f8079add68b4307edb0e63e61b347 [diff] |
Adding bytecode verification. This moves much of the interpreter checks to an ahead-of-time bytecode verifier. This allows us to share the same verification with JITs and disable it entirely for code size reasons using the `-DIREE_VM_BYTECODE_VERIFICATION_ENABLE=0` compiler flag. Verification is pretty exhaustive but may still need some additions. It's significantly better than before, though, so even if not the final form it's a good step. Simpler verification (and dispatch) will come with a pending bytecode shuffling into instruction classes.
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.