[Bug analyzer/98223] gcc.dg/analyzer/pr94851-1.c XPASSes

2021-01-05 Thread dmalcolm at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98223 David Malcolm changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|---

[Bug analyzer/98223] gcc.dg/analyzer/pr94851-1.c XPASSes

2021-01-05 Thread cvs-commit at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98223 --- Comment #4 from CVS Commits --- The master branch has been updated by David Malcolm : https://gcc.gnu.org/g:df1eba3ceada6e8990c00ccfa6c5a2c9b1c13334 commit r11-6495-gdf1eba3ceada6e8990c00ccfa6c5a2c9b1c13334 Author: David Malcolm Date: Tu

[Bug analyzer/98223] gcc.dg/analyzer/pr94851-1.c XPASSes

2021-01-05 Thread dmalcolm at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98223 --- Comment #3 from David Malcolm --- i.e. it rejects the path as infeasible since p_2 needs to be NULL and then non-NULL for the path conditions to be satisfied

[Bug analyzer/98223] gcc.dg/analyzer/pr94851-1.c XPASSes

2021-01-05 Thread dmalcolm at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98223 --- Comment #2 from David Malcolm --- I believe the existing false positive may relate to bug 97072, where the analyzer doesn't capture that the pointer to the malloc-ed buffer has been written to one of the fields (perhaps due to state-merging),

[Bug analyzer/98223] gcc.dg/analyzer/pr94851-1.c XPASSes

2021-01-04 Thread dmalcolm at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98223 David Malcolm changed: What|Removed |Added Status|UNCONFIRMED |ASSIGNED Ever confirmed|0

[Bug analyzer/98223] gcc.dg/analyzer/pr94851-1.c XPASSes

2020-12-10 Thread ro at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98223 Rainer Orth changed: What|Removed |Added Target Milestone|--- |11.0