This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Status of GCC memory checking, -fcheck-memory-usage

From: Tristan Gingold <tgingold at ipricot dot com>
To: "Joseph S. Myers" <jsm28 at cam dot ac dot uk>
Cc: Alexandre Oliva <aoliva at redhat dot com>, AWLaFramboise at aol dot com, gcc at gcc dot gnu dot org, Theodore dot Papadopoulo at sophia dot inria dot fr, lars dot spam at nocrew dot org, tgingold at ipricot dot com
Date: Mon, 11 Feb 2002 08:03:38 +0000
Subject: Re: Status of GCC memory checking, -fcheck-memory-usage
References: <or66569irk.fsf@free.redhat.lsd.ic.unicamp.br> <Pine.LNX.4.33.0202101150030.2871-100000@kern.srcf.societies.cam.ac.uk>

On Sun, Feb 10, 2002 at 11:51:26AM +0000, Joseph S. Myers wrote:
> On 10 Feb 2002, Alexandre Oliva wrote:
> 
> > If anyone feels like
> > resurrecting this feature, the patch that took the feature out can
> > always be used as a starting point/
> 
> It should not be used as a starting point.  The previous implementation
> was too pervasive; for example, people working on built-in string
> functions should not need to know the details of -fcheck-memory-usage.
I agree with you.
Only after adding the -fcheck-memory-usage feature to GCC, I had understood
that GCC was not really shaped for such a feature.  That's a reason why it was
very difficult to maintain the -fcheck-memory-usage inside GCC.

Tristan.

References:
- Re: Status of GCC memory checking, -fcheck-memory-usage
  - From: Alexandre Oliva
- Re: Status of GCC memory checking, -fcheck-memory-usage
  - From: Joseph S. Myers

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]