On 9/10/20 7:36 AM, David Malcolm wrote:
BTW, in terms of analyzer issues, my big rewrite of analyzer state- tracking landed in master a month ago, on 2020-08-13 as 808f4dfeb3a95f50f15e71148e5c1067f90a126d, and changed the behavior of gcc.dg/analyzer/explode-2.c, which was one of the ones an earlier version of Sandra's patch also affected.
In case I failed to make this explicit previously: my 2020-08-13 patch did not trigger the analyzer regressions in C that the version from last fall did, because it retains the existing form of C lowering for loops.
Sandra: was the most recent patch you posted tested against a relatively recent source tree? (i.e. since that 2020-08-13 patch?). That said, I don't want the analyzer to stand in the way of improvements to the frontends, so let me know if I can help with any analyzer testsuite regressions.
I did not prepare a rebased patch set against mainline head, but I did just rebase, rebuild, and retest these patches earlier this week in conjunction with the OpenACC kernels loop annotation patches that depend on them, that I just posted yesterday. I didn't see any analyzer regressions in those test results either.
-Sandra
