NagyDonat wrote:

> Invalidation is nothing complicated. Enumerate the arguments and escape them. 
> This is all the default eval call does anyway.

Fair point, I didn't recall the exact details and thought that the default eval 
is a bit more complicated. We can say that the function 
`justPerformConservativeEvaluation` that I proposed already exists under the 
name `CallEvent::InvalidateRegions`.

@gamesh411 As this `evalCall` based approach seems to be very straightforward, 
I would suggest that instead of the current PR you should create a new hidden 
modeling checker (e.g. `ForcedOpaqueCallChecker` or find a better name) which 
is enabled by default (e.g. place it in the `core` group) and has an `evalCall` 
callback that forces conservative evaluation for the problematic functions.

Later, as a separate commit, you (or somebody else) could move the existing 
suppressions to this new checker.

https://github.com/llvm/llvm-project/pull/177804
_______________________________________________
cfe-commits mailing list
[email protected]
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits

Reply via email to