[Bug analyzer/97568] -fanalyzer assumes that an extern const pointer is NULL

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

[Bug analyzer/97568] -fanalyzer assumes that an extern const pointer is NULL

2020-10-27 Thread cvs-commit at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97568 --- Comment #3 from CVS Commits --- The master branch has been updated by David Malcolm : https://gcc.gnu.org/g:16ad9ae85bb5b9acf80f9d1cf2be5a989ef7ba49 commit r11-4437-g16ad9ae85bb5b9acf80f9d1cf2be5a989ef7ba49 Author: David Malcolm Date: Tu

[Bug analyzer/97568] -fanalyzer assumes that an extern const pointer is NULL

2020-10-26 Thread dmalcolm at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97568 David Malcolm changed: What|Removed |Added Ever confirmed|0 |1 Last reconfirmed|

[Bug analyzer/97568] -fanalyzer assumes that an extern const pointer is NULL

2020-10-25 Thread vincent-gcc at vinc17 dot net via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97568 --- Comment #1 from Vincent Lefèvre --- The bug has been introduced by commit af66094d037793773eb8a49597866457f2f6a104.