[PATCH] D136162: [analyzer] Fix assertion failure with conflicting prototype calls

Balázs Benics via Phabricator via cfe-commits cfe-commits at lists.llvm.org
Thu Oct 20 08:02:59 PDT 2022


steakhal added a comment.

In D136162#3869645 <https://reviews.llvm.org/D136162#3869645>, @NoQ wrote:

>> In this example, we try to store 42 to the Elem{buffer, 0}.
>
> In this case the natural question is, why does it go through `bindArray()`? We're not binding an array. Can we try to preserve the contract that `bindArray()` only deals with arrays?
>
> @martong's comment makes sense to me, it sounds like this could be a case of `CallEvent::getRuntimeDefinition()` not picking up the right definition, at least not consistently.

Thank you @martong and @NoQ for the helpful comments. They really helped a lot to look at this problem from a new perspective!
I hope, this new approach is more aligned with your expectations.


Repository:
  rG LLVM Github Monorepo

CHANGES SINCE LAST ACTION
  https://reviews.llvm.org/D136162/new/

https://reviews.llvm.org/D136162



More information about the cfe-commits mailing list