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: Diego Novillo <dnovillo at google dot com>
To: Andrew Haley <aph at redhat dot com>
Cc: "Kaveh R. Ghazi" <ghazi at caip dot rutgers dot edu>, tromey at redhat dot com, 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 17:09:04 -0500
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> <000401c85884$227db450$6501a8c0@glap> <18318.29762.339001.265706@zebedee.pink>

On 1/16/08 4:16 PM, Andrew Haley wrote:

Because it's not a bug?  You're changing the code to silence a false
negative, which this is what we here in England call "putting the cart
before the horse."  If we clean up all the memory regions on closedown
we'll be wasting CPU time.  And for what?

I agree. Freeing memory right before we exit is a waste of time.

Diego.

Follow-Ups:
- RE: Memory leaks in compiler
  - From: Dave Korn

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
- Re: Memory leaks in compiler
  - From: Kaveh R. Ghazi
- Re: Memory leaks in compiler
  - From: Andrew Haley

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