Analyzer: Split setjmp/longjmp implementation to its own file
The GCC analyzer's `setjmp`/`longjmp` handling is now in its own file for better code organization.
The GCC static analyzer’s implementation for handling setjmp and longjmp has been moved into a dedicated file (setjmp-longjmp.cc). This change improves code organization and maintainability without altering the analyzer’s functionality. The commit moves functions and data structures related to setjmp and longjmp from analyzer.cc, engine.cc, and region-model.cc into the new file. This separation clarifies the codebase and makes it easier to work on the analyzer’s setjmp/longjmp support.
In Details
The GCC static analyzer needs special handling for setjmp and longjmp because they alter the control flow in non-obvious ways. This commit refactors the analyzer's code by moving the setjmp/longjmp-related logic into setjmp-longjmp.cc. This change affects Makefile.in, analyzer.cc, engine.cc, region-model.cc, and svalue.cc. This is a refactoring; other parts of the compiler are unlikely to depend directly on these analyzer internals.
For Context
setjmp and longjmp are C functions that allow a program to jump from one point in the code to another, even across function boundaries. The GCC static analyzer needs to understand how these functions affect the program's control flow in order to accurately detect potential errors. This commit improves the organization of the analyzer's code by moving the implementation for handling setjmp and longjmp into its own file. This change makes the analyzer's code easier to understand and maintain, without changing its behavior.