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: Memory leaks in compiler

From: "Kaveh R. Ghazi" <ghazi at caip dot rutgers dot edu>
To: <tromey at redhat dot com>
Cc: "Vincent Lefevre" <vincent+gcc at vinc17 dot org>, <gcc at gcc dot gnu dot org>, "Jerry DeLisle" <jvdelisle at verizon dot net>
Date: Wed, 16 Jan 2008 14:09:49 -0700
Subject: Re: Memory leaks in compiler
References: <4787C3C4.5020909@verizon.net><20080111203135.GA8113@prunille.vinc17.org><Pine.GSO.4.58.0801160022270.19987@caipclassic.rutgers.edu> <m37ii9bnn1.fsf@fleche.redhat.com>

From: "Tom Tromey" <tromey@redhat.com>

"Kaveh" == Kaveh R GHAZI <ghazi@caip.rutgers.edu> writes:
Kaveh> + mpfr_free_cache ();
Why not just add a valgrind suppression for this?
There's little point in freeing things just before exit.
Tom

A valgrind suppression only silences the error for valgrind. What if someone uses another memory checking tool? Better to fix it for real IMHO.

       --Kaveh
--
Kaveh R. Ghazi

Follow-Ups:
- Re: Memory leaks in compiler
  - From: Andrew Haley
- Re: Memory leaks in compiler
  - From: Tom Tromey

References:
- Memory leaks in compiler
  - From: Jerry DeLisle
- Re: Memory leaks in compiler
  - From: Vincent Lefevre
- Re: Memory leaks in compiler
  - From: Kaveh R. GHAZI
- Re: Memory leaks in compiler
  - From: Tom Tromey

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