Tune compiler tracing usage of 'frame's. (#15216) Compiler tracing was a bit confusing when profiling to find https://github.com/openxla/iree/issues/15209. First, this fixes an issue where frame frames were unbalanced upon recursing into the compiler, leading to confusing rendering in the Tracy UI that could misattribute sections of the compiler running to the "GlobalOptimization" pass pipeline:  Second, this tweaks how frames are defined for unnamed pipelines and adds a scope for bytecode translation (which happens outside of a pass pipeline): 
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.