From 937d37ef78d3ef445335928d498422083df74d77 Mon Sep 17 00:00:00 2001 From: Andres Noetzli Date: Tue, 2 Oct 2018 14:55:21 -0700 Subject: Make registration of preprocessing passes explicit (#2564) As it turns out, self-registering types are problematic with static linkage [0]. Instead of fixing the issue with linker flags, which seems possible but also brittle (e.g. the flags may be different for different linkers), this commit adds an explicit registration of each preprocessing pass. [0] https://www.bfilipek.com/2018/02/static-vars-static-lib.html --- src/preprocessing/passes/nl_ext_purify.cpp | 2 -- 1 file changed, 2 deletions(-) (limited to 'src/preprocessing/passes/nl_ext_purify.cpp') diff --git a/src/preprocessing/passes/nl_ext_purify.cpp b/src/preprocessing/passes/nl_ext_purify.cpp index 630f35c14..744bd8ad8 100644 --- a/src/preprocessing/passes/nl_ext_purify.cpp +++ b/src/preprocessing/passes/nl_ext_purify.cpp @@ -16,7 +16,6 @@ #include "preprocessing/passes/nl_ext_purify.h" -#include "preprocessing/preprocessing_pass_registry.h" namespace CVC4 { namespace preprocessing { @@ -127,7 +126,6 @@ PreprocessingPassResult NlExtPurify::applyInternal( return PreprocessingPassResult::NO_CONFLICT; } -static RegisterPass X("nl-ext-purify"); } // namespace passes } // namespace preprocessing -- cgit v1.2.3