PhASAR's Releases

PhASAR's Releases

Version Format

PhASAR uses the CalVer version format.

Since v2403, PhASAR has updated its version format from v{MM}{YY} to:

v{YY}{MM}

So, the version v1118 was released in November 2018, but v2403 was released in March 2024.

Version Compatibility

APIs from different PhASAR releases may not be compatible with each other. We document API-breaks in BreakingChanges.md.

Within two different versions of the development branch that belong to the same release, breaking changes are expected to be less, but we cannot rule them out entirely. We aim for marking obsolete APIs with [[deprecated]] wherever possible. These APIs will be removed right after the next release.

ABI compatibility is a non-goal. Since PhASAR heavily relies on templates, ABI compatibility does not make much sense.

PhASAR released versions

Version	Description
v2604	April Release 2026. For more information, please see v2604.
v2510	October Release 2025. For more information, please see v2510.
v2503	March Release 2025. For more information, please see v2503.
v2403	March Release 2024. For more information, please see v2403.
v0323	March Release 2023. Probably the last one supporting LLVM 14. For more information, please see v0323.
v1222	Christmas Release 2022. See v1222 for details.
v0120	add content of version here.
v0619	add content of version here.
v0319	Contains a first implementation of a solver that uses weighted push-down systems to solve inter-procedural data-flow problems. The constructors of the LLVM-based problem descriptions have been adjusted such that a user's analysis code has easier access (in addition to the inter-procedural control-flow graph) to the type hierarchy and function-wise points-to graphs that can be retrieved through the ProjectIRDB reference.
v1218	Contains some minor bugfixed and improvements. isFieldLoad() and isFieldStore() functionalities have been added to the control-flow infrastructure. These functions will be of use in the near future in order to implement more precise points-to analyses. Additionally, backward-control-flow capabilities have been added allowing for backward analysis (additional unit tests have to be written, still). In order to distinguish C++'s special member functions, isSpecialMemberFunction() has been introduced. This function allows to check if a function is a constructor, destructor, etc.
v1118	Contains fixed vtable access and support for C-style variadic functions in the pre-defined LLVM-based flow functions MapFactsToCallee and MapFactsToCaller. Added additional LLVM-based flow functions PropagateLoad and PropagateStore. The measurement mechanism PAMM has been overhauled. The C++17 standard may be used from now on: The OSX Travis build is stalled until we update to a newer LLVM version. This is because LLVM-5.0.1 uses STL features that have been removed in C++17. GCC's implementation libstdc++, however, still has them, whereas Clang's libc++ removed them. On OSX try to install gcc-7 in order to get libstdc++ or try to change the standard to C++14 in CMakeLists.txt, however, we will move towards using C++17 features in the near future. Released on Nov 3rd 2018 .
v1018	Second version which contains a minor update including bug fixes, improved code quality released on Oct 9th 2018.
v-pldi18	PhASAR framework first version was released on 14th June 2018 and presented at the PLDI 2018 conference held in Philadelphia, Pennsylvania, United States.