[llvm-branch-commits] [clang] Backport to 20.x "[clang][analyzer] Fix error path of builtin overflow (#136345)" (PR #136589)

2025-04-22 Thread Pavel Skripkin via llvm-branch-commits
pskrgag wrote: > Then issue the "git cherry-pick -x HASH" command and force push to your > branch. I've done that locally (+ fixed merge conflicts) and commit message is the same as in original patch. I've only changed the PR title https://github.com/llvm/llvm-project/pull/136589

[llvm-branch-commits] [clang] Backport to 20.x "[clang][analyzer] Fix error path of builtin overflow (#136345)" (PR #136589)

2025-04-21 Thread Pavel Skripkin via llvm-branch-commits
pskrgag wrote: Hm, I guess I've done smth wrong, since merge button is not available? Sorry, I am doing llvm backports for the first time https://github.com/llvm/llvm-project/pull/136589 ___ llvm-branch-commits mailing list llvm-branch-commits@lists.l

[llvm-branch-commits] [clang] Backport to 20.x "[clang][analyzer] Fix error path of builtin overflow (#136345)" (PR #136589)

2025-04-21 Thread Pavel Skripkin via llvm-branch-commits
https://github.com/pskrgag created https://github.com/llvm/llvm-project/pull/136589 According to https://clang.llvm.org/docs/LanguageExtensions.html#checked-arithmetic-builtins, result of builtin_*_overflow functions will be initialized even in case of overflow. Align analyzer logic to docs an