class OuterAnalysisManagerProxy

Declaration

template <typename AnalysisManagerT,
          typename IRUnitT,
          typename... ExtraArgTs>
class OuterAnalysisManagerProxy { /* full declaration omitted */ };

Description

An analysis over an "inner" IR unit that provides access to an analysis manager over a "outer" IR unit. The inner unit must be contained in the outer unit. For example OuterAnalysisManagerProxy <ModuleAnalysisManager , Function> is an analysis over Functions (the "inner" unit) which provides access to a Module analysis manager. The ModuleAnalysisManager is the "outer" manager being proxied, and Modules are the "outer" IR unit. The inner/outer relationship is valid because each Function is contained in one Module. This proxy only exposes the const interface of the outer analysis manager, to indicate that you cannot cause an outer analysis to run from within an inner pass. Instead, you must rely on the \c getCachedResult API. This proxy doesn't manage invalidation in any way -- that is handled by the recursive return path of each layer of the pass manager. A consequence of this is the outer analyses may be stale. We invalidate the outer analyses only when we're done running passes over the inner IR units.

Declared at: llvm/include/llvm/IR/PassManager.h:1161

Templates

AnalysisManagerT
IRUnitT
ExtraArgTs

Method Overview

Methods

OuterAnalysisManagerProxy<AnalysisManagerT,
                          IRUnitT,
                          ExtraArgTs...>(
    const AnalysisManagerT& OuterAM)

Declared at: llvm/include/llvm/IR/PassManager.h:1230

Parameters

const AnalysisManagerT& OuterAM

llvm::OuterAnalysisManagerProxy::Result run(
    IRUnitT&,
    AnalysisManager<IRUnitT, ExtraArgTs...>&,
    ExtraArgTs...)

Description

Run the analysis pass and create our proxy result object. Nothing to see here, it just forwards the \c OuterAM reference into the result.

Declared at: llvm/include/llvm/IR/PassManager.h:1236

Parameters

IRUnitT&
AnalysisManager<IRUnitT, ExtraArgTs...>&
ExtraArgTs...