From 2441bbaec303801f2e869ba72fa36a5f6058ef3d Mon Sep 17 00:00:00 2001 From: Fabian Schiebel Date: Mon, 19 Oct 2026 19:50:33 +0200 Subject: [PATCH 1/2] Bump v2610 --- BreakingChanges.md | 4 ++++ CMakeLists.txt | 2 +- examples/use-phasar-with-fetch-content/CMakeLists.txt | 2 +- 3 files changed, 6 insertions(+), 2 deletions(-) diff --git a/BreakingChanges.md b/BreakingChanges.md index 77da5377ba..a950462b65 100644 --- a/BreakingChanges.md +++ b/BreakingChanges.md @@ -2,6 +2,10 @@ ## development HEAD +- *None* + +## v2610 + - Existing IFDS/IDE problems provided by PhASAR do no longer inherit from `IFDSTabulationProblem`/`IDETabulationProblem`. The solvers can now deal with them without polymorphic inheritance hierarchy. However, **you cannot cast an analysis problem to one of these base classes anymore**. If that's required (unlikely), wrap your problem in a `LegacyIDEProblemWrapper`. - Although the IFDS/IDETabulationProblem classes still work, new IFDS/IDE analysis problems should conform to the `IFDSProblem`/`IDEProblem` concepts instead. Use `IfdsIdeProblemMixin` as helper for that. - `IDESolver` and `IFDSSolver` now take analysis problems by pointer instead of by reference to better document that they capture the address (without taking ownership). diff --git a/CMakeLists.txt b/CMakeLists.txt index f02b3cc2e7..a6f5a9144c 100644 --- a/CMakeLists.txt +++ b/CMakeLists.txt @@ -21,7 +21,7 @@ if (DEFINED LLVM_MAIN_SRC_DIR) set(PHASAR_IN_TREE 1) endif() -set(PHASAR_VERSION 2604) +set(PHASAR_VERSION 2610) if (NOT PHASAR_IN_TREE) project (phasar LANGUAGES C CXX diff --git a/examples/use-phasar-with-fetch-content/CMakeLists.txt b/examples/use-phasar-with-fetch-content/CMakeLists.txt index 026e29fcee..9195fc4fe5 100644 --- a/examples/use-phasar-with-fetch-content/CMakeLists.txt +++ b/examples/use-phasar-with-fetch-content/CMakeLists.txt @@ -11,7 +11,7 @@ include(FetchContent) FetchContent_Declare( phasar GIT_REPOSITORY https://github.com/secure-software-engineering/phasar.git - GIT_TAG development # At best, use a tagged version, such as v2604 + GIT_TAG development # At best, use a tagged version, such as v2610 EXCLUDE_FROM_ALL OVERRIDE_FIND_PACKAGE ) From 7c9be9960494ae03bac3476d664ff05568e9bd05 Mon Sep 17 00:00:00 2001 From: Fabian Schiebel <52407375+fabianbs96@users.noreply.github.com> Date: Sat, 24 Oct 2026 12:28:01 +0200 Subject: [PATCH 2/2] Fix typo in BreakingChanges --- BreakingChanges.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/BreakingChanges.md b/BreakingChanges.md index a950462b65..c8805cfbb8 100644 --- a/BreakingChanges.md +++ b/BreakingChanges.md @@ -12,7 +12,7 @@ - `FlowFunctionPtrType` is now a move-only type. - Removed the CRTP-template `ProjectIRDBBase`. Use the concept `ProjectIRDB` instead. - Removed `EdgeFunction::equals`. Use `operator==` instead. -- Removed ctor-overloads of `LLVMProjectIRDB` that use the `EnableOpaquePointers` parameter. LLVM is removing support for opaque pointers. Use the other ctors instead. +- Removed ctor-overloads of `LLVMProjectIRDB` that use the `EnableOpaquePointers` parameter. LLVM is removing support for non-opaque pointers. Use the other ctors instead. - Removed type-trait `has_getAsJson`, as it is not used in our codebase anymore. We switched from `getAsJson` to `printAsJson` a while ago. ## v2604