Remove the static_analysist framework.

This has been deprecated for many many years and only had one user
which was a more obscure feature of goto-instrument.  ait is better
in almost every direction.

Author: martin-cs

src/analyses/Makefile

@@ -29,7 +29,6 @@ SRC = ai.cpp \
       locals.cpp \
       reaching_definitions.cpp \
       sese_regions.cpp \
-      static_analysis.cpp \
       uncaught_exceptions_analysis.cpp \
       uninitialized_domain.cpp \
       variable-sensitivity/abstract_environment.cpp \

src/analyses/README.md

@@ -8,9 +8,8 @@ static analyses that instantiate them.
 
 \section analyses-frameworks Frameworks:
 
-There are currently three abstract interpretation frameworks provided in this
-directory. \ref analyses-ait, \ref analyses-flow-insensitive-analysis, and the
-deprecated and obsolete \ref analyses-static-analysist.
+There are currently two abstract interpretation frameworks provided in this
+directory. \ref analyses-ait and \ref analyses-flow-insensitive-analysis.
 
 \subsection analyses-ait Abstract interpreter framework (ait)
 
@@ -22,14 +21,6 @@ is provided by \ref ait. This analysis framework is currently location sensitive
 run after the function pointer removal and return removal passes. There is
 ongoing work to make this framework also support context sensitivity.
 
-\subsection analyses-static-analysist Old Abstract interpreter framework (static_analysist)
-
-The obsolete static analysis framework \ref static_analysist is only used by
-\ref value_set_analysist. This abstract interpretation framework is deprecated in
-favour of \ref analyses-ait, and should not be used as the basis for new code.
-This framework is location sensitive (one domain per code location), but is able
-to be run before function pointer removal and return removal phases.
-
 \subsection analyses-flow-insensitive-analysis Flow-insensitive analysis (flow_insensitive_analysist)
 
 Framework for flow-insensitive analyses. Maintains a single global abstract