2014-03-19 19:41:38 +01:00
|
|
|
//===- PassManager.cpp - Infrastructure for managing & running IR passes --===//
|
2013-11-13 02:12:08 +01:00
|
|
|
//
|
|
|
|
// The LLVM Compiler Infrastructure
|
|
|
|
//
|
|
|
|
// This file is distributed under the University of Illinois Open Source
|
|
|
|
// License. See LICENSE.TXT for details.
|
|
|
|
//
|
|
|
|
//===----------------------------------------------------------------------===//
|
|
|
|
|
|
|
|
#include "llvm/ADT/STLExtras.h"
|
2014-05-16 04:33:15 +02:00
|
|
|
#include "llvm/IR/LLVMContext.h"
|
2014-01-11 12:52:05 +01:00
|
|
|
#include "llvm/IR/PassManager.h"
|
|
|
|
#include "llvm/Support/CommandLine.h"
|
|
|
|
#include "llvm/Support/Debug.h"
|
2013-11-13 02:12:08 +01:00
|
|
|
|
|
|
|
using namespace llvm;
|
|
|
|
|
2014-01-11 12:52:05 +01:00
|
|
|
static cl::opt<bool>
|
|
|
|
DebugPM("debug-pass-manager", cl::Hidden,
|
|
|
|
cl::desc("Print pass management debugging information"));
|
|
|
|
|
[PM] Switch analysis managers to be threaded through the run methods
rather than the constructors of passes.
This simplifies the APIs of passes significantly and removes an error
prone pattern where the *same* manager had to be given to every
different layer. With the new API the analysis managers themselves will
have to be cross connected with proxy analyses that allow a pass at one
layer to query for the analysis manager of another layer. The proxy will
both expose a handle to the other layer's manager and it will provide
the invalidation hooks to ensure things remain consistent across layers.
Finally, the outer-most analysis manager has to be passed to the run
method of the outer-most pass manager. The rest of the propagation is
automatic.
I've used SFINAE again to allow passes to completely disregard the
analysis manager if they don't need or want to care. This helps keep
simple things simple for users of the new pass manager.
Also, the system specifically supports passing a null pointer into the
outer-most run method if your pass pipeline neither needs nor wants to
deal with analyses. I find this of dubious utility as while some
*passes* don't care about analysis, I'm not sure there are any
real-world users of the pass manager itself that need to avoid even
creating an analysis manager. But it is easy to support, so there we go.
Finally I renamed the module proxy for the function analysis manager to
the more verbose but less confusing name of
FunctionAnalysisManagerModuleProxy. I hate this name, but I have no idea
what else to name these things. I'm expecting in the fullness of time to
potentially have the complete cross product of types at the proxy layer:
{Module,SCC,Function,Loop,Region}AnalysisManager{Module,SCC,Function,Loop,Region}Proxy
(except for XAnalysisManagerXProxy which doesn't make any sense)
This should make it somewhat easier to do the next phases which is to
build the upward proxy and get its invalidation correct, as well as to
make the invalidation within the Module -> Function mapping pass be more
fine grained so as to invalidate fewer fuction analyses.
After all of the proxy analyses are done and the invalidation working,
I'll finally be able to start working on the next two fun fronts: how to
adapt an existing pass to work in both the legacy pass world and the new
one, and building the SCC, Loop, and Region counterparts. Fun times!
llvm-svn: 195400
2013-11-22 01:43:29 +01:00
|
|
|
PreservedAnalyses ModulePassManager::run(Module *M, ModuleAnalysisManager *AM) {
|
2013-11-20 12:31:50 +01:00
|
|
|
PreservedAnalyses PA = PreservedAnalyses::all();
|
2014-01-11 12:52:05 +01:00
|
|
|
|
|
|
|
if (DebugPM)
|
|
|
|
dbgs() << "Starting module pass manager run.\n";
|
|
|
|
|
2013-11-20 12:31:50 +01:00
|
|
|
for (unsigned Idx = 0, Size = Passes.size(); Idx != Size; ++Idx) {
|
2014-01-11 12:52:05 +01:00
|
|
|
if (DebugPM)
|
|
|
|
dbgs() << "Running module pass: " << Passes[Idx]->name() << "\n";
|
|
|
|
|
[PM] Switch analysis managers to be threaded through the run methods
rather than the constructors of passes.
This simplifies the APIs of passes significantly and removes an error
prone pattern where the *same* manager had to be given to every
different layer. With the new API the analysis managers themselves will
have to be cross connected with proxy analyses that allow a pass at one
layer to query for the analysis manager of another layer. The proxy will
both expose a handle to the other layer's manager and it will provide
the invalidation hooks to ensure things remain consistent across layers.
Finally, the outer-most analysis manager has to be passed to the run
method of the outer-most pass manager. The rest of the propagation is
automatic.
I've used SFINAE again to allow passes to completely disregard the
analysis manager if they don't need or want to care. This helps keep
simple things simple for users of the new pass manager.
Also, the system specifically supports passing a null pointer into the
outer-most run method if your pass pipeline neither needs nor wants to
deal with analyses. I find this of dubious utility as while some
*passes* don't care about analysis, I'm not sure there are any
real-world users of the pass manager itself that need to avoid even
creating an analysis manager. But it is easy to support, so there we go.
Finally I renamed the module proxy for the function analysis manager to
the more verbose but less confusing name of
FunctionAnalysisManagerModuleProxy. I hate this name, but I have no idea
what else to name these things. I'm expecting in the fullness of time to
potentially have the complete cross product of types at the proxy layer:
{Module,SCC,Function,Loop,Region}AnalysisManager{Module,SCC,Function,Loop,Region}Proxy
(except for XAnalysisManagerXProxy which doesn't make any sense)
This should make it somewhat easier to do the next phases which is to
build the upward proxy and get its invalidation correct, as well as to
make the invalidation within the Module -> Function mapping pass be more
fine grained so as to invalidate fewer fuction analyses.
After all of the proxy analyses are done and the invalidation working,
I'll finally be able to start working on the next two fun fronts: how to
adapt an existing pass to work in both the legacy pass world and the new
one, and building the SCC, Loop, and Region counterparts. Fun times!
llvm-svn: 195400
2013-11-22 01:43:29 +01:00
|
|
|
PreservedAnalyses PassPA = Passes[Idx]->run(M, AM);
|
2013-11-20 12:31:50 +01:00
|
|
|
if (AM)
|
|
|
|
AM->invalidate(M, PassPA);
|
2014-03-02 05:08:41 +01:00
|
|
|
PA.intersect(std::move(PassPA));
|
2014-05-16 04:33:15 +02:00
|
|
|
|
|
|
|
M->getContext().yield();
|
2013-11-20 12:31:50 +01:00
|
|
|
}
|
2014-01-11 12:52:05 +01:00
|
|
|
|
|
|
|
if (DebugPM)
|
|
|
|
dbgs() << "Finished module pass manager run.\n";
|
|
|
|
|
2013-11-20 12:31:50 +01:00
|
|
|
return PA;
|
2013-11-13 02:12:08 +01:00
|
|
|
}
|
|
|
|
|
2014-02-05 22:41:42 +01:00
|
|
|
ModuleAnalysisManager::ResultConceptT &
|
[PM] Split the analysis manager into a function-specific interface and
a module-specific interface. This is the first of many steps necessary
to generalize the infrastructure such that we can support both
a Module-to-Function and Module-to-SCC-to-Function pass manager
nestings.
After a *lot* of attempts that never worked and didn't even make it to
a committable state, it became clear that I had gotten the layering
design of analyses flat out wrong. Four days later, I think I have most
of the plan for how to correct this, and I'm starting to reshape the
code into it. This is just a baby step I'm afraid, but starts separating
the fundamentally distinct concepts of function analysis passes and
module analysis passes so that in subsequent steps we can effectively
layer them, and have a consistent design for the eventual SCC layer.
As part of this, I've started some interface changes to make passes more
regular. The module pass accepts the module in the run method, and some
of the constructor parameters are gone. I'm still working out exactly
where constructor parameters vs. method parameters will be used, so
I expect this to fluctuate a bit.
This actually makes the invalidation less "correct" at this phase,
because now function passes don't invalidate module analysis passes, but
that was actually somewhat of a misfeature. It will return in a better
factored form which can scale to other units of IR. The documentation
has gotten less verbose and helpful.
llvm-svn: 195189
2013-11-20 05:01:38 +01:00
|
|
|
ModuleAnalysisManager::getResultImpl(void *PassID, Module *M) {
|
2013-11-13 02:12:08 +01:00
|
|
|
ModuleAnalysisResultMapT::iterator RI;
|
|
|
|
bool Inserted;
|
2014-03-02 14:30:33 +01:00
|
|
|
std::tie(RI, Inserted) = ModuleAnalysisResults.insert(std::make_pair(
|
2014-03-09 12:49:53 +01:00
|
|
|
PassID, std::unique_ptr<detail::AnalysisResultConcept<Module *>>()));
|
2013-11-13 02:12:08 +01:00
|
|
|
|
2013-11-26 12:24:37 +01:00
|
|
|
// If we don't have a cached result for this module, look up the pass and run
|
|
|
|
// it to produce a result, which we then add to the cache.
|
|
|
|
if (Inserted)
|
2014-07-16 19:09:21 +02:00
|
|
|
RI->second = lookupPass(PassID).run(M, this);
|
2013-11-13 02:12:08 +01:00
|
|
|
|
|
|
|
return *RI->second;
|
|
|
|
}
|
|
|
|
|
2014-02-05 22:41:42 +01:00
|
|
|
ModuleAnalysisManager::ResultConceptT *
|
2013-11-23 01:38:42 +01:00
|
|
|
ModuleAnalysisManager::getCachedResultImpl(void *PassID, Module *M) const {
|
2014-03-10 03:12:14 +01:00
|
|
|
ModuleAnalysisResultMapT::const_iterator RI =
|
|
|
|
ModuleAnalysisResults.find(PassID);
|
2014-04-09 08:08:46 +02:00
|
|
|
return RI == ModuleAnalysisResults.end() ? nullptr : &*RI->second;
|
2013-11-23 01:38:42 +01:00
|
|
|
}
|
|
|
|
|
[PM] Split the analysis manager into a function-specific interface and
a module-specific interface. This is the first of many steps necessary
to generalize the infrastructure such that we can support both
a Module-to-Function and Module-to-SCC-to-Function pass manager
nestings.
After a *lot* of attempts that never worked and didn't even make it to
a committable state, it became clear that I had gotten the layering
design of analyses flat out wrong. Four days later, I think I have most
of the plan for how to correct this, and I'm starting to reshape the
code into it. This is just a baby step I'm afraid, but starts separating
the fundamentally distinct concepts of function analysis passes and
module analysis passes so that in subsequent steps we can effectively
layer them, and have a consistent design for the eventual SCC layer.
As part of this, I've started some interface changes to make passes more
regular. The module pass accepts the module in the run method, and some
of the constructor parameters are gone. I'm still working out exactly
where constructor parameters vs. method parameters will be used, so
I expect this to fluctuate a bit.
This actually makes the invalidation less "correct" at this phase,
because now function passes don't invalidate module analysis passes, but
that was actually somewhat of a misfeature. It will return in a better
factored form which can scale to other units of IR. The documentation
has gotten less verbose and helpful.
llvm-svn: 195189
2013-11-20 05:01:38 +01:00
|
|
|
void ModuleAnalysisManager::invalidateImpl(void *PassID, Module *M) {
|
|
|
|
ModuleAnalysisResults.erase(PassID);
|
|
|
|
}
|
|
|
|
|
2013-11-26 12:24:37 +01:00
|
|
|
void ModuleAnalysisManager::invalidateImpl(Module *M,
|
|
|
|
const PreservedAnalyses &PA) {
|
|
|
|
// FIXME: This is a total hack based on the fact that erasure doesn't
|
|
|
|
// invalidate iteration for DenseMap.
|
|
|
|
for (ModuleAnalysisResultMapT::iterator I = ModuleAnalysisResults.begin(),
|
|
|
|
E = ModuleAnalysisResults.end();
|
|
|
|
I != E; ++I)
|
|
|
|
if (I->second->invalidate(M, PA))
|
|
|
|
ModuleAnalysisResults.erase(I);
|
|
|
|
}
|
|
|
|
|
2014-03-10 03:12:14 +01:00
|
|
|
PreservedAnalyses FunctionPassManager::run(Function *F,
|
|
|
|
FunctionAnalysisManager *AM) {
|
2013-11-20 12:31:50 +01:00
|
|
|
PreservedAnalyses PA = PreservedAnalyses::all();
|
2014-01-11 12:52:05 +01:00
|
|
|
|
|
|
|
if (DebugPM)
|
|
|
|
dbgs() << "Starting function pass manager run.\n";
|
|
|
|
|
2013-11-20 12:31:50 +01:00
|
|
|
for (unsigned Idx = 0, Size = Passes.size(); Idx != Size; ++Idx) {
|
2014-01-11 12:52:05 +01:00
|
|
|
if (DebugPM)
|
|
|
|
dbgs() << "Running function pass: " << Passes[Idx]->name() << "\n";
|
|
|
|
|
[PM] Switch analysis managers to be threaded through the run methods
rather than the constructors of passes.
This simplifies the APIs of passes significantly and removes an error
prone pattern where the *same* manager had to be given to every
different layer. With the new API the analysis managers themselves will
have to be cross connected with proxy analyses that allow a pass at one
layer to query for the analysis manager of another layer. The proxy will
both expose a handle to the other layer's manager and it will provide
the invalidation hooks to ensure things remain consistent across layers.
Finally, the outer-most analysis manager has to be passed to the run
method of the outer-most pass manager. The rest of the propagation is
automatic.
I've used SFINAE again to allow passes to completely disregard the
analysis manager if they don't need or want to care. This helps keep
simple things simple for users of the new pass manager.
Also, the system specifically supports passing a null pointer into the
outer-most run method if your pass pipeline neither needs nor wants to
deal with analyses. I find this of dubious utility as while some
*passes* don't care about analysis, I'm not sure there are any
real-world users of the pass manager itself that need to avoid even
creating an analysis manager. But it is easy to support, so there we go.
Finally I renamed the module proxy for the function analysis manager to
the more verbose but less confusing name of
FunctionAnalysisManagerModuleProxy. I hate this name, but I have no idea
what else to name these things. I'm expecting in the fullness of time to
potentially have the complete cross product of types at the proxy layer:
{Module,SCC,Function,Loop,Region}AnalysisManager{Module,SCC,Function,Loop,Region}Proxy
(except for XAnalysisManagerXProxy which doesn't make any sense)
This should make it somewhat easier to do the next phases which is to
build the upward proxy and get its invalidation correct, as well as to
make the invalidation within the Module -> Function mapping pass be more
fine grained so as to invalidate fewer fuction analyses.
After all of the proxy analyses are done and the invalidation working,
I'll finally be able to start working on the next two fun fronts: how to
adapt an existing pass to work in both the legacy pass world and the new
one, and building the SCC, Loop, and Region counterparts. Fun times!
llvm-svn: 195400
2013-11-22 01:43:29 +01:00
|
|
|
PreservedAnalyses PassPA = Passes[Idx]->run(F, AM);
|
2013-11-20 12:31:50 +01:00
|
|
|
if (AM)
|
|
|
|
AM->invalidate(F, PassPA);
|
2014-03-02 05:08:41 +01:00
|
|
|
PA.intersect(std::move(PassPA));
|
2014-05-16 04:33:15 +02:00
|
|
|
|
|
|
|
F->getContext().yield();
|
2013-11-20 12:31:50 +01:00
|
|
|
}
|
2014-01-11 12:52:05 +01:00
|
|
|
|
|
|
|
if (DebugPM)
|
|
|
|
dbgs() << "Finished function pass manager run.\n";
|
|
|
|
|
2013-11-20 12:31:50 +01:00
|
|
|
return PA;
|
[PM] Split the analysis manager into a function-specific interface and
a module-specific interface. This is the first of many steps necessary
to generalize the infrastructure such that we can support both
a Module-to-Function and Module-to-SCC-to-Function pass manager
nestings.
After a *lot* of attempts that never worked and didn't even make it to
a committable state, it became clear that I had gotten the layering
design of analyses flat out wrong. Four days later, I think I have most
of the plan for how to correct this, and I'm starting to reshape the
code into it. This is just a baby step I'm afraid, but starts separating
the fundamentally distinct concepts of function analysis passes and
module analysis passes so that in subsequent steps we can effectively
layer them, and have a consistent design for the eventual SCC layer.
As part of this, I've started some interface changes to make passes more
regular. The module pass accepts the module in the run method, and some
of the constructor parameters are gone. I'm still working out exactly
where constructor parameters vs. method parameters will be used, so
I expect this to fluctuate a bit.
This actually makes the invalidation less "correct" at this phase,
because now function passes don't invalidate module analysis passes, but
that was actually somewhat of a misfeature. It will return in a better
factored form which can scale to other units of IR. The documentation
has gotten less verbose and helpful.
llvm-svn: 195189
2013-11-20 05:01:38 +01:00
|
|
|
}
|
|
|
|
|
2013-11-21 03:11:31 +01:00
|
|
|
bool FunctionAnalysisManager::empty() const {
|
|
|
|
assert(FunctionAnalysisResults.empty() ==
|
|
|
|
FunctionAnalysisResultLists.empty() &&
|
|
|
|
"The storage and index of analysis results disagree on how many there "
|
|
|
|
"are!");
|
|
|
|
return FunctionAnalysisResults.empty();
|
|
|
|
}
|
|
|
|
|
|
|
|
void FunctionAnalysisManager::clear() {
|
|
|
|
FunctionAnalysisResults.clear();
|
|
|
|
FunctionAnalysisResultLists.clear();
|
|
|
|
}
|
|
|
|
|
2014-02-05 22:41:42 +01:00
|
|
|
FunctionAnalysisManager::ResultConceptT &
|
[PM] Split the analysis manager into a function-specific interface and
a module-specific interface. This is the first of many steps necessary
to generalize the infrastructure such that we can support both
a Module-to-Function and Module-to-SCC-to-Function pass manager
nestings.
After a *lot* of attempts that never worked and didn't even make it to
a committable state, it became clear that I had gotten the layering
design of analyses flat out wrong. Four days later, I think I have most
of the plan for how to correct this, and I'm starting to reshape the
code into it. This is just a baby step I'm afraid, but starts separating
the fundamentally distinct concepts of function analysis passes and
module analysis passes so that in subsequent steps we can effectively
layer them, and have a consistent design for the eventual SCC layer.
As part of this, I've started some interface changes to make passes more
regular. The module pass accepts the module in the run method, and some
of the constructor parameters are gone. I'm still working out exactly
where constructor parameters vs. method parameters will be used, so
I expect this to fluctuate a bit.
This actually makes the invalidation less "correct" at this phase,
because now function passes don't invalidate module analysis passes, but
that was actually somewhat of a misfeature. It will return in a better
factored form which can scale to other units of IR. The documentation
has gotten less verbose and helpful.
llvm-svn: 195189
2013-11-20 05:01:38 +01:00
|
|
|
FunctionAnalysisManager::getResultImpl(void *PassID, Function *F) {
|
2013-11-13 02:12:08 +01:00
|
|
|
FunctionAnalysisResultMapT::iterator RI;
|
|
|
|
bool Inserted;
|
2014-03-02 14:30:33 +01:00
|
|
|
std::tie(RI, Inserted) = FunctionAnalysisResults.insert(std::make_pair(
|
2013-11-13 02:12:08 +01:00
|
|
|
std::make_pair(PassID, F), FunctionAnalysisResultListT::iterator()));
|
|
|
|
|
2013-11-26 12:24:37 +01:00
|
|
|
// If we don't have a cached result for this function, look up the pass and
|
|
|
|
// run it to produce a result, which we then add to the cache.
|
2013-11-13 02:12:08 +01:00
|
|
|
if (Inserted) {
|
|
|
|
FunctionAnalysisResultListT &ResultList = FunctionAnalysisResultLists[F];
|
2014-03-09 12:49:53 +01:00
|
|
|
ResultList.emplace_back(PassID, lookupPass(PassID).run(F, this));
|
2014-03-02 13:27:27 +01:00
|
|
|
RI->second = std::prev(ResultList.end());
|
2013-11-13 02:12:08 +01:00
|
|
|
}
|
|
|
|
|
|
|
|
return *RI->second->second;
|
|
|
|
}
|
|
|
|
|
2014-02-05 22:41:42 +01:00
|
|
|
FunctionAnalysisManager::ResultConceptT *
|
2013-11-23 01:38:42 +01:00
|
|
|
FunctionAnalysisManager::getCachedResultImpl(void *PassID, Function *F) const {
|
|
|
|
FunctionAnalysisResultMapT::const_iterator RI =
|
|
|
|
FunctionAnalysisResults.find(std::make_pair(PassID, F));
|
2014-04-09 08:08:46 +02:00
|
|
|
return RI == FunctionAnalysisResults.end() ? nullptr : &*RI->second->second;
|
2013-11-23 01:38:42 +01:00
|
|
|
}
|
|
|
|
|
[PM] Split the analysis manager into a function-specific interface and
a module-specific interface. This is the first of many steps necessary
to generalize the infrastructure such that we can support both
a Module-to-Function and Module-to-SCC-to-Function pass manager
nestings.
After a *lot* of attempts that never worked and didn't even make it to
a committable state, it became clear that I had gotten the layering
design of analyses flat out wrong. Four days later, I think I have most
of the plan for how to correct this, and I'm starting to reshape the
code into it. This is just a baby step I'm afraid, but starts separating
the fundamentally distinct concepts of function analysis passes and
module analysis passes so that in subsequent steps we can effectively
layer them, and have a consistent design for the eventual SCC layer.
As part of this, I've started some interface changes to make passes more
regular. The module pass accepts the module in the run method, and some
of the constructor parameters are gone. I'm still working out exactly
where constructor parameters vs. method parameters will be used, so
I expect this to fluctuate a bit.
This actually makes the invalidation less "correct" at this phase,
because now function passes don't invalidate module analysis passes, but
that was actually somewhat of a misfeature. It will return in a better
factored form which can scale to other units of IR. The documentation
has gotten less verbose and helpful.
llvm-svn: 195189
2013-11-20 05:01:38 +01:00
|
|
|
void FunctionAnalysisManager::invalidateImpl(void *PassID, Function *F) {
|
2013-11-15 22:44:35 +01:00
|
|
|
FunctionAnalysisResultMapT::iterator RI =
|
|
|
|
FunctionAnalysisResults.find(std::make_pair(PassID, F));
|
2013-11-13 02:12:08 +01:00
|
|
|
if (RI == FunctionAnalysisResults.end())
|
|
|
|
return;
|
|
|
|
|
|
|
|
FunctionAnalysisResultLists[F].erase(RI->second);
|
2013-11-26 12:24:37 +01:00
|
|
|
}
|
|
|
|
|
|
|
|
void FunctionAnalysisManager::invalidateImpl(Function *F,
|
|
|
|
const PreservedAnalyses &PA) {
|
|
|
|
// Clear all the invalidated results associated specifically with this
|
|
|
|
// function.
|
|
|
|
SmallVector<void *, 8> InvalidatedPassIDs;
|
|
|
|
FunctionAnalysisResultListT &ResultsList = FunctionAnalysisResultLists[F];
|
|
|
|
for (FunctionAnalysisResultListT::iterator I = ResultsList.begin(),
|
|
|
|
E = ResultsList.end();
|
|
|
|
I != E;)
|
|
|
|
if (I->second->invalidate(F, PA)) {
|
|
|
|
InvalidatedPassIDs.push_back(I->first);
|
|
|
|
I = ResultsList.erase(I);
|
|
|
|
} else {
|
|
|
|
++I;
|
|
|
|
}
|
|
|
|
while (!InvalidatedPassIDs.empty())
|
|
|
|
FunctionAnalysisResults.erase(
|
|
|
|
std::make_pair(InvalidatedPassIDs.pop_back_val(), F));
|
2014-04-21 13:11:54 +02:00
|
|
|
if (ResultsList.empty())
|
|
|
|
FunctionAnalysisResultLists.erase(F);
|
2013-11-13 02:12:08 +01:00
|
|
|
}
|
2013-11-21 03:11:31 +01:00
|
|
|
|
[PM] Switch analysis managers to be threaded through the run methods
rather than the constructors of passes.
This simplifies the APIs of passes significantly and removes an error
prone pattern where the *same* manager had to be given to every
different layer. With the new API the analysis managers themselves will
have to be cross connected with proxy analyses that allow a pass at one
layer to query for the analysis manager of another layer. The proxy will
both expose a handle to the other layer's manager and it will provide
the invalidation hooks to ensure things remain consistent across layers.
Finally, the outer-most analysis manager has to be passed to the run
method of the outer-most pass manager. The rest of the propagation is
automatic.
I've used SFINAE again to allow passes to completely disregard the
analysis manager if they don't need or want to care. This helps keep
simple things simple for users of the new pass manager.
Also, the system specifically supports passing a null pointer into the
outer-most run method if your pass pipeline neither needs nor wants to
deal with analyses. I find this of dubious utility as while some
*passes* don't care about analysis, I'm not sure there are any
real-world users of the pass manager itself that need to avoid even
creating an analysis manager. But it is easy to support, so there we go.
Finally I renamed the module proxy for the function analysis manager to
the more verbose but less confusing name of
FunctionAnalysisManagerModuleProxy. I hate this name, but I have no idea
what else to name these things. I'm expecting in the fullness of time to
potentially have the complete cross product of types at the proxy layer:
{Module,SCC,Function,Loop,Region}AnalysisManager{Module,SCC,Function,Loop,Region}Proxy
(except for XAnalysisManagerXProxy which doesn't make any sense)
This should make it somewhat easier to do the next phases which is to
build the upward proxy and get its invalidation correct, as well as to
make the invalidation within the Module -> Function mapping pass be more
fine grained so as to invalidate fewer fuction analyses.
After all of the proxy analyses are done and the invalidation working,
I'll finally be able to start working on the next two fun fronts: how to
adapt an existing pass to work in both the legacy pass world and the new
one, and building the SCC, Loop, and Region counterparts. Fun times!
llvm-svn: 195400
2013-11-22 01:43:29 +01:00
|
|
|
char FunctionAnalysisManagerModuleProxy::PassID;
|
2013-11-21 03:11:31 +01:00
|
|
|
|
[PM] Switch analysis managers to be threaded through the run methods
rather than the constructors of passes.
This simplifies the APIs of passes significantly and removes an error
prone pattern where the *same* manager had to be given to every
different layer. With the new API the analysis managers themselves will
have to be cross connected with proxy analyses that allow a pass at one
layer to query for the analysis manager of another layer. The proxy will
both expose a handle to the other layer's manager and it will provide
the invalidation hooks to ensure things remain consistent across layers.
Finally, the outer-most analysis manager has to be passed to the run
method of the outer-most pass manager. The rest of the propagation is
automatic.
I've used SFINAE again to allow passes to completely disregard the
analysis manager if they don't need or want to care. This helps keep
simple things simple for users of the new pass manager.
Also, the system specifically supports passing a null pointer into the
outer-most run method if your pass pipeline neither needs nor wants to
deal with analyses. I find this of dubious utility as while some
*passes* don't care about analysis, I'm not sure there are any
real-world users of the pass manager itself that need to avoid even
creating an analysis manager. But it is easy to support, so there we go.
Finally I renamed the module proxy for the function analysis manager to
the more verbose but less confusing name of
FunctionAnalysisManagerModuleProxy. I hate this name, but I have no idea
what else to name these things. I'm expecting in the fullness of time to
potentially have the complete cross product of types at the proxy layer:
{Module,SCC,Function,Loop,Region}AnalysisManager{Module,SCC,Function,Loop,Region}Proxy
(except for XAnalysisManagerXProxy which doesn't make any sense)
This should make it somewhat easier to do the next phases which is to
build the upward proxy and get its invalidation correct, as well as to
make the invalidation within the Module -> Function mapping pass be more
fine grained so as to invalidate fewer fuction analyses.
After all of the proxy analyses are done and the invalidation working,
I'll finally be able to start working on the next two fun fronts: how to
adapt an existing pass to work in both the legacy pass world and the new
one, and building the SCC, Loop, and Region counterparts. Fun times!
llvm-svn: 195400
2013-11-22 01:43:29 +01:00
|
|
|
FunctionAnalysisManagerModuleProxy::Result
|
|
|
|
FunctionAnalysisManagerModuleProxy::run(Module *M) {
|
2014-03-13 10:50:31 +01:00
|
|
|
assert(FAM->empty() && "Function analyses ran prior to the module proxy!");
|
|
|
|
return Result(*FAM);
|
2013-11-21 03:11:31 +01:00
|
|
|
}
|
|
|
|
|
[PM] Switch analysis managers to be threaded through the run methods
rather than the constructors of passes.
This simplifies the APIs of passes significantly and removes an error
prone pattern where the *same* manager had to be given to every
different layer. With the new API the analysis managers themselves will
have to be cross connected with proxy analyses that allow a pass at one
layer to query for the analysis manager of another layer. The proxy will
both expose a handle to the other layer's manager and it will provide
the invalidation hooks to ensure things remain consistent across layers.
Finally, the outer-most analysis manager has to be passed to the run
method of the outer-most pass manager. The rest of the propagation is
automatic.
I've used SFINAE again to allow passes to completely disregard the
analysis manager if they don't need or want to care. This helps keep
simple things simple for users of the new pass manager.
Also, the system specifically supports passing a null pointer into the
outer-most run method if your pass pipeline neither needs nor wants to
deal with analyses. I find this of dubious utility as while some
*passes* don't care about analysis, I'm not sure there are any
real-world users of the pass manager itself that need to avoid even
creating an analysis manager. But it is easy to support, so there we go.
Finally I renamed the module proxy for the function analysis manager to
the more verbose but less confusing name of
FunctionAnalysisManagerModuleProxy. I hate this name, but I have no idea
what else to name these things. I'm expecting in the fullness of time to
potentially have the complete cross product of types at the proxy layer:
{Module,SCC,Function,Loop,Region}AnalysisManager{Module,SCC,Function,Loop,Region}Proxy
(except for XAnalysisManagerXProxy which doesn't make any sense)
This should make it somewhat easier to do the next phases which is to
build the upward proxy and get its invalidation correct, as well as to
make the invalidation within the Module -> Function mapping pass be more
fine grained so as to invalidate fewer fuction analyses.
After all of the proxy analyses are done and the invalidation working,
I'll finally be able to start working on the next two fun fronts: how to
adapt an existing pass to work in both the legacy pass world and the new
one, and building the SCC, Loop, and Region counterparts. Fun times!
llvm-svn: 195400
2013-11-22 01:43:29 +01:00
|
|
|
FunctionAnalysisManagerModuleProxy::Result::~Result() {
|
2013-11-21 03:11:31 +01:00
|
|
|
// Clear out the analysis manager if we're being destroyed -- it means we
|
|
|
|
// didn't even see an invalidate call when we got invalidated.
|
2014-03-13 10:50:31 +01:00
|
|
|
FAM->clear();
|
2013-11-21 03:11:31 +01:00
|
|
|
}
|
|
|
|
|
[PM] Switch analysis managers to be threaded through the run methods
rather than the constructors of passes.
This simplifies the APIs of passes significantly and removes an error
prone pattern where the *same* manager had to be given to every
different layer. With the new API the analysis managers themselves will
have to be cross connected with proxy analyses that allow a pass at one
layer to query for the analysis manager of another layer. The proxy will
both expose a handle to the other layer's manager and it will provide
the invalidation hooks to ensure things remain consistent across layers.
Finally, the outer-most analysis manager has to be passed to the run
method of the outer-most pass manager. The rest of the propagation is
automatic.
I've used SFINAE again to allow passes to completely disregard the
analysis manager if they don't need or want to care. This helps keep
simple things simple for users of the new pass manager.
Also, the system specifically supports passing a null pointer into the
outer-most run method if your pass pipeline neither needs nor wants to
deal with analyses. I find this of dubious utility as while some
*passes* don't care about analysis, I'm not sure there are any
real-world users of the pass manager itself that need to avoid even
creating an analysis manager. But it is easy to support, so there we go.
Finally I renamed the module proxy for the function analysis manager to
the more verbose but less confusing name of
FunctionAnalysisManagerModuleProxy. I hate this name, but I have no idea
what else to name these things. I'm expecting in the fullness of time to
potentially have the complete cross product of types at the proxy layer:
{Module,SCC,Function,Loop,Region}AnalysisManager{Module,SCC,Function,Loop,Region}Proxy
(except for XAnalysisManagerXProxy which doesn't make any sense)
This should make it somewhat easier to do the next phases which is to
build the upward proxy and get its invalidation correct, as well as to
make the invalidation within the Module -> Function mapping pass be more
fine grained so as to invalidate fewer fuction analyses.
After all of the proxy analyses are done and the invalidation working,
I'll finally be able to start working on the next two fun fronts: how to
adapt an existing pass to work in both the legacy pass world and the new
one, and building the SCC, Loop, and Region counterparts. Fun times!
llvm-svn: 195400
2013-11-22 01:43:29 +01:00
|
|
|
bool FunctionAnalysisManagerModuleProxy::Result::invalidate(
|
|
|
|
Module *M, const PreservedAnalyses &PA) {
|
2013-11-23 00:38:07 +01:00
|
|
|
// If this proxy isn't marked as preserved, then we can't even invalidate
|
|
|
|
// individual function analyses, there may be an invalid set of Function
|
|
|
|
// objects in the cache making it impossible to incrementally preserve them.
|
|
|
|
// Just clear the entire manager.
|
|
|
|
if (!PA.preserved(ID()))
|
2014-03-13 10:50:31 +01:00
|
|
|
FAM->clear();
|
2013-11-21 03:11:31 +01:00
|
|
|
|
|
|
|
// Return false to indicate that this result is still a valid proxy.
|
|
|
|
return false;
|
|
|
|
}
|
2013-11-23 02:25:07 +01:00
|
|
|
|
|
|
|
char ModuleAnalysisManagerFunctionProxy::PassID;
|