Add a doFinalization method to the DataLayout pass.

This pass is meant to be immutable, however it holds mutable state to cache StructLayouts.
This method will allow the pass manager to clear the mutable state between runs.

Note that unfortunately it is still necessary to have the destructor, even though it does the
same thing as doFinalization.  This is because most TargetMachines embed a DataLayout on which
doFinalization isn't run as its never added to the pass manager.

I also didn't think it was necessary to complication things with a deInit method for which
doFinalization and ~DataLayout both call as there's only one field of mutable state.  If we had
more fields to finalize i'd have added this.

llvm-svn: 176877
This commit is contained in:
Pete Cooper 2013-03-12 17:37:31 +00:00
parent 74d9647d18
commit 7a5199df98
2 changed files with 10 additions and 0 deletions

View File

@ -181,6 +181,10 @@ public:
~DataLayout(); // Not virtual, do not subclass this class
/// DataLayout is an immutable pass, but holds state. This allows the pass
/// manager to clear its mutable state.
bool doFinalization(Module &M);
/// Parse a data layout string (with fallback to default values). Ensure that
/// the data layout pass is registered.
void init(StringRef LayoutDescription);

View File

@ -438,6 +438,12 @@ DataLayout::~DataLayout() {
delete static_cast<StructLayoutMap*>(LayoutMap);
}
bool DataLayout::doFinalization(Module &M) {
delete static_cast<StructLayoutMap*>(LayoutMap);
LayoutMap = 0;
return false;
}
const StructLayout *DataLayout::getStructLayout(StructType *Ty) const {
if (!LayoutMap)
LayoutMap = new StructLayoutMap();