| commit | d01a83ca3011fcc6efdde8577d9b11363d87d9ca | [log] [tgz] |
|---|---|---|
| author | bjacob <benoitjacob@google.com> | Mon Jul 10 16:39:18 2023 -0400 |
| committer | GitHub <noreply@github.com> | Mon Jul 10 20:39:18 2023 +0000 |
| tree | b2d20345476b03043efcfe902877a20924f11e59 | |
| parent | 80b694ff818c3d41bfcc97e4e56d4ac3de824a99 [diff] |
Make ukernel code inlinable down to arch-specific function pointer selection. (#14283)
Fixes #14262 .
Unused ukernel code paths (e.g. different data types, different SIMD
variants) were not getting DCE'd as intended.
Code paths ("tile funcs") are selected by `*_select_tile_func_arch`
functions, so in order for unused code paths to be DCE'd, these
functions must be inlined. There were two problems preventing them from
being inlined:
1. They had different target attributes. That's because these
architecture-specific tile function selection functions were built with
architecture-specific flags, while their caller was generic 64-bit code
(built as wasm_64 and stripped of target attributes).
* This is solved by moving these functions to separate `_entry_point.c`
files, which are built as architecture-generic code to match their
callers to make them effectively inlinable.
3. They were not marked as internal linkage by the time we run DCE, in
`runLLVMIRPasses`. The `fixupVisibility` function marks all functions as
internal linkage, but only after `runLLVMIRPasses`.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.