This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c/50606] gcc fails to detect obvious use of NULL pointer
- From: "manu at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Sun, 13 May 2012 22:46:42 +0000
- Subject: [Bug c/50606] gcc fails to detect obvious use of NULL pointer
- Auto-submitted: auto-generated
- References: <bug-50606-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50606
Manuel LÃpez-IbÃÃez <manu at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |manu at gcc dot gnu.org
--- Comment #1 from Manuel LÃpez-IbÃÃez <manu at gcc dot gnu.org> 2012-05-13 22:46:42 UTC ---
printf warnings are handled in the FE, so we would need constant-propagation in
the FE. Clang implements it, so I know it is possible. However, no current
contributor to GCC has enough time and interest to implement it, so unless some
new contributors appear, don't expect this anytime soon.