Analyzer: Split exploded_path into its own files
The GCC analyzer's `exploded_path` implementation has been split into separate files for better organization.
The GCC static analyzer’s exploded_path functionality has been reorganized by moving its implementation into dedicated files (exploded-path.cc and exploded-path.h). This refactoring improves code modularity and maintainability without introducing any functional changes. The change involves moving the definition of the exploded_path class and its associated methods from engine.cc and exploded-graph.h to the new files, and updating include directives accordingly. This change makes the analyzer’s codebase easier to navigate and modify.
In Details
The GCC static analyzer uses an exploded_graph to represent the program's execution paths, and exploded_path represents a single such path. This commit reorganizes the code by splitting the exploded_path implementation into exploded-path.cc and exploded-path.h. The affected files include Makefile.in, diagnostic-manager.cc, engine.cc, exploded-graph.h, feasible-graph.cc, exploded-path.cc, and exploded-path.h. This is primarily a refactoring to improve code organization; other parts of the compiler are unlikely to depend directly on these analyzer internals.
For Context
The GCC static analyzer examines code to identify potential errors before the program is run. It uses a graph-like data structure to represent different possible execution paths through the code. This commit reorganizes the analyzer's internal code by separating the implementation of a key component, exploded_path, into its own files. This type of change improves the structure and maintainability of the analyzer's code, making it easier for developers to understand and modify the analyzer's behavior. This doesn't directly affect the analyzer's functionality or the warnings it produces.