This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c/30475] assert(int+100 > int) optimized away
- From: "kargl at gcc dot gnu dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 23 Jan 2007 00:45:52 -0000
- Subject: [Bug c/30475] assert(int+100 > int) optimized away
- References: <bug-30475-3511@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #52 from kargl at gcc dot gnu dot org 2007-01-23 00:45 -------
(In reply to comment #51)
> Sure, new security checks can be written in a compliant manner.
>
> But what plan do you suggest to find instances of non-compliant overflow
> checking in the existing body? Think something like a whole Linux
> distribution. Something in the order of 15000 packages. Dozens of millions of
> lines of code. Any suggestion?
>
How about http://scan.coverity.com/
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30475