search for: mamproxi

Introduction ============ This RFC proposes a mechanism to dump arbitrary messages into object files during compilation and retrieve them from the final executable. Background ========== We often need to collect information from all object files of applications. For example: - Mircea Trofin needs to collect information from the function inlining pass so that he can train the machine

On 3/14/19 2:04 AM, Hiroshi Yamauchi wrote: > > > On Wed, Mar 13, 2019 at 2:37 PM Fedor Sergeev <fedor.sergeev at azul.com > <mailto:fedor.sergeev at azul.com>> wrote: > >> >> - Add a new proxy ModuleAnalysisManagerLoopProxy for a loop pass >> to be able to get to the ModuleAnalysisManager in one step and >> PSI through it. >

I think that we should think about the relationship between this proposed mechanism and the existing mechanism that we have for emitting and capturing optimization remarks. In some sense, I feel like we already have a lot of this capability (e.g., llc has -remarks-section).  -Hal On 8/5/20 5:51 PM, Johannes Doerfert via llvm-dev wrote: > I like the ability, not sure about the proposed

Overall seems fine to me. On 3/11/19 8:12 PM, Hiroshi Yamauchi wrote: > Here's a revised approach based on the discussion: > > - Cache PSI right after the profile summary in the IR is written in > the pass pipeline. This would avoid the need to insert > RequireAnalysisPass for PSI before each non-module pass that needs it. > PSI can be technically invalidated but unlikely

On Wed, Aug 5, 2020 at 3:51 PM Eli Friedman <efriedma at quicinc.com> wrote: > I’m not a fan of keeping important data outside the IR in an analysis. If > we’re planning to emit it, it should be represented directly in the IR. Is > there some reason we can’t just stick the data in a global variable? > The analysis in the scenarios here is external to LLVM - ML training, for