This is the mail archive of the
mailing list for the GCC project.
Re: Status of GCC memory checking, -fcheck-memory-usage
- From: Tristan Gingold <tgingold at ipricot dot com>
- To: Theodore Papadopoulo <Theodore dot Papadopoulo at sophia dot inria dot fr>
- Cc: Tristan Gingold <tgingold at ipricot dot com>, Lars Brinkhoff <lars dot spam at nocrew dot org>, Carlo Wood <carlo at alinoe dot com>, AWLaFramboise at aol dot com, gcc at gcc dot gnu dot org
- Date: Mon, 11 Feb 2002 08:14:18 +0000
- Subject: Re: Status of GCC memory checking, -fcheck-memory-usage
- References: <firstname.lastname@example.org> <200202081545.g18FjkP25095@mururoa.inria.fr>
On Fri, Feb 08, 2002 at 04:45:46PM +0100, Theodore Papadopoulo wrote:
> What is the difference of -fcheck-memory-usage and the bounds
> checking that was tried and still survives at:
I think bounds checking is able to check array/pointer dereferencing in some
Checker is only able to check memory accesses, such as reading uninitialized
memory or reading/writing to forbidden memory (the work is to make this
consistent, and it was).
Checker can check array bounds, but only as a side effect.