-
Notifications
You must be signed in to change notification settings - Fork 13.2k
Merge r347981 into the 7.0 branch #39194
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
assigned to @tstellar |
Artem, is this OK to merge to the release_70 branch? |
Also Devin, since you are the code owner, what do you think? |
I approve merging. It looks like a very safe patch to me: it merely disables a new feature in certain scenarios, reverting to the old behavior. |
Ádám are you able to port this test case to the release_70 branch. It looks like it uses some helper functions that aren't in the branch. |
Oh yes, Artem updated the tests recently using a new feature. I changed it to the old format and committed it to the release_70 branch. However I can only see an LLVM commit (https://reviews.llvm.org/rL348362) but no Clang commit (no https://reviews.llvm.org/rC348362). Also the automatic mail to llvm-branch-commits is waiting for the moderator. I keep this bug open until you confirm that my commit was successful. |
I can confirm this was merged: r348362. |
Extended Description
[Analyzer] [HOTFIX!] SValBuilder crash when
aggressive-binary-operation-simplification
enabledDuring the review of D41938 a condition check with an early exit accidentally slipped into a branch, leaving the other branch unprotected. This may result in an assertion later on. This hotfix moves this contition check outside of the branch.
Commit: https://reviews.llvm.org/rC347981
The text was updated successfully, but these errors were encountered: