[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|--- |FIXED

--- Comment #4 from David Malcolm  ---
Should be fixed by the above commit.

[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:   Tue Oct 27 09:54:25 2020 -0400

analyzer: don't assume extern const vars are zero-initialized [PR97568]

gcc/analyzer/ChangeLog:
PR analyzer/97568
* region-model.cc (region_model::get_initial_value_for_global):
Move check that !DECL_EXTERNAL from here to...
* region.cc (decl_region::get_svalue_for_initializer): ...here,
using it to reject zero initialization.

gcc/testsuite/ChangeLog:
PR analyzer/97568
* gcc.dg/analyzer/pr97568.c: New test.

[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||2020-10-26
 Status|UNCONFIRMED |ASSIGNED

--- Comment #2 from David Malcolm  ---
Thanks for filing this; confirmed.  I'm working on a fix.

[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.