| commit | be1a5f4469d2947b4a00cf07c143d7552f00fd8c | [log] [tgz] |
|---|---|---|
| author | Scott Todd <scott.todd0@gmail.com> | Thu Apr 04 14:31:36 2024 -0700 |
| committer | GitHub <noreply@github.com> | Thu Apr 04 14:31:36 2024 -0700 |
| tree | 6dbc45f1c899bdf56f63a805a56f3186e907593c | |
| parent | f20186298a025a4f0cb562e12f0071669af2079e [diff] |
Document testing policy and external test suite. (#16982) Having a documented "test policy" is one of the checkboxes for https://www.bestpractices.dev/en : > The project MUST have a general policy (formal or not) that as major new functionality is added to the software produced by the project, tests of that functionality should be added to an automated test suite. As long as a policy is in place, even by word of mouth, that says developers should add tests to the automated test suite for major new functionality, select "Met." We've had an informal policy, but this makes it more explicit. --- While touching testing docs, I also added a section for https://github.com/nod-ai/SHARK-TestSuite/ and how that is integrated into this repo.
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.