balazske wrote: The checker had only a few results from the usual C projects where we test it, but more of these are difficult to understand.
[This](https://codechecker-demo.eastus.cloudapp.azure.com/Default/report-detail?run=vim_v8.2.1920_fixedaddr_on_test&newcheck=vim_v8.2.1920_fixedaddr_off_test&diff-type=Resolved&report-id=6949477&report-hash=51821bc4cedc89e884af3e1013e4398d&report-filepath=vim%2Fsrc%2Fregexp_bt.c) (vim) result is not a false positive, at the line above (3127) a function `regnext(scan)` is called and the execution path goes over branch conditions where `scan` becomes equal to a constant value. But this fact is hardly visible to the user. In [this](https://codechecker-demo.eastus.cloudapp.azure.com/Default/report-detail?run=postgres_REL_13_0_fixedaddr_on_test&newcheck=postgres_REL_13_0_fixedaddr_off_test&diff-type=Resolved&report-id=6952310&report-hash=bb74d2cc7ed487d5ce1e4cede31a309d&report-filepath=postgres%2Fsrc%2Fbackend%2Fcommands%2Fpolicy.c) (postgres) example I could not find out what causes the fixed value to appear, probably it has to do something with the long macro expansions. https://github.com/llvm/llvm-project/pull/132404 _______________________________________________ cfe-commits mailing list cfe-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
