range-ops: Use const/static where possible
This commit improves code clarity and reduces potential errors by adding `const` and `static` keywords to range-ops functions and variables.
This commit refactors the range-ops code to use const and static where appropriate. This improves code clarity, may offer slight performance improvements by enabling better compiler optimizations due to immutability guarantees, and reduces the risk of unintended modification of data. No functional change is intended.
In Details
This change modifies range-op-float.cc, range-op-ptr.cc, range-op.cc, and range-op.h to add const and static keywords to various functions and variables within the range-ops subsystem. It also fixes a typo in a comment and uses nullptr instead of 0 where appropriate. The primary goal is to improve code maintainability and readability without introducing functional changes.
For Context
This commit improves the internal structure of a part of the GCC compiler responsible for analyzing the possible range of values that variables can hold. By adding the keywords const and static to certain functions and variables, the code becomes more self-documenting and easier to understand. const indicates that a value will not be changed, while static limits the visibility of a function or variable to the current file. These changes help to prevent accidental errors and improve the overall quality of the compiler's code.