Remove support to store IsolationNode objects in flyweights
There is not an easy approach to comparing two isolation nodes without a
detailed comparison of the node's capture registers, rules, and child
nodes. This would be an expensive comparison. Instead, the isolation
nodes will be managed by the containing isolation chip objects.
Change-Id: Ia0171d752bc2efc912feaaa0ed387a3b4a24a881
Signed-off-by: Zane Shelley <zshelle@us.ibm.com>
diff --git a/src/isolator/hei_isolator.cpp b/src/isolator/hei_isolator.cpp
index e4266b0..3488ab9 100644
--- a/src/isolator/hei_isolator.cpp
+++ b/src/isolator/hei_isolator.cpp
@@ -32,13 +32,9 @@
void Isolator::uninitialize()
{
- // Clear all of the IsolationChip objects.
+ // Clear all of the isolation objects.
iv_isoChips.clear();
- // Remove all of the IsolationNode objects stored in the flyweights. This
- // must be done before removing the HardwareRegister objects
- Flyweight<const IsolationNode>::getSingleton().clear();
-
// Must flush the hardware register cache before deleting any
// HardwareRegister objects.
HardwareRegister::flushAll();