| commit | 71a994559068929f206ca60b764416ebfe65daa2 | [log] [tgz] |
|---|---|---|
| author | Ben Vanik <ben.vanik@gmail.com> | Thu May 02 13:16:09 2024 -0700 |
| committer | GitHub <noreply@github.com> | Thu May 02 13:16:09 2024 -0700 |
| tree | dc05cdd2d3e16cb43d624cafd69f2df9ce621243 | |
| parent | 61a226348ed72ec96b7b304ffe925b3ea5f9674a [diff] |
Adding `--iree-opt-import-parameters=` and cleaning up export. (#16828)
The new option allows for importing all or some parameters from a
parameter file into the compiler. One or more parameter files to one or
more scopes can be specified, just as with the
`--parameters=[scope=]file.*` flag in the runtime tool. If a scope is
provided only parameters with that scope will be imported. If a
parameter (optionally within a scope) is named explicitly it will be
imported. If a maximum size is specified all parameters <= that size
will be imported.
The export pass has been reworked to be the inverse of the import such
that it's possible to round-trip through export and import. The import
pass doesn't currently support all of the types we can export as
`SerializableAttrInterface` doesn't have a deserialize method (yet) and
we need special handling of packed types (i1, i4, etc). For now warnings
are emitted and the globals are left as parameter references to still
allow partial imports.
Flag renames:
* `--iree-opt-parameter-archive-export-file=` +
`--iree-opt-parameter-archive-export-scope=` ->
`--iree-opt-export-parameters=[scope=]file`
* `--iree-opt-minimum-parameter-export-size=` ->
`--iree-opt-export-parameter-minimum-size=`
* `--iree-opt-splat-parameter-archive-export-file=` ->
`--iree-opt-splat-parameters=`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.