From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 407 invoked by alias); 22 Oct 2011 01:31:19 -0000 Received: (qmail 398 invoked by uid 22791); 22 Oct 2011 01:31:18 -0000 X-SWARE-Spam-Status: No, hits=-1.1 required=5.0 tests=AWL,BAYES_00,RDNS_DYNAMIC,TVD_RCVD_IP X-Spam-Check-By: sourceware.org Received: from 195-14-0-142.nuxit.net (HELO de558.ispfr.net) (195.14.0.142) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Sat, 22 Oct 2011 01:30:56 +0000 Received: from ours.starynkevitch.net ([213.41.244.95] helo=glinka.lesours) by de558.ispfr.net with smtp (Exim 4.72) (envelope-from ) id 1RHQQH-0001Yk-Sk; Sat, 22 Oct 2011 03:30:54 +0200 Date: Sat, 22 Oct 2011 11:20:00 -0000 From: Basile Starynkevitch To: Gabriel Dos Reis Cc: gcc@gcc.gnu.org Subject: Re: adding destroyable objects into Ggc Message-Id: <20111022033044.2b491fd5f56b892823595146@starynkevitch.net> In-Reply-To: References: <20111018171201.361304028ab94f102f827bd2@starynkevitch.net> <20111018191350.470cd6b1cd291373d5ff3f2c@starynkevitch.net> <20111020080753.a895eae452bb25e312ebf617@starynkevitch.net> <20111020081245.GA12085@ours.starynkevitch.net> <20111020085324.GA12472@ours.starynkevitch.net> <20111021080914.08528e83f5eb53897d92fee9@starynkevitch.net> <20111021225635.d0b5fe0b81daeb82a503dafd@starynkevitch.net> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org X-SW-Source: 2011-10/txt/msg00397.txt.bz2 On Fri, 21 Oct 2011 18:53:16 -0500 Gabriel Dos Reis wrote: > On Fri, Oct 21, 2011 at 3:56 PM, Basile Starynkevitch > wrote: > > On Fri, 21 Oct 2011 10:43:29 +0200 > > Richard Guenther wrote: > >> So there is no inherent limitation with the GGC machinery. > > > > There are at least some annoyances: > > can you think of C++ ways to remove those without prescribing more GC? I don't have enough knowledge and practice of C++ for that. I am expecting C++ gurus to explain how they'll do. And I strongly believe that a garbage collector is an asset in a compiler, not an annoyance. My belief is that, if Ggc has some weaknesses, it could be improved, and not avoided. Because my belief is that a good garbage collector solve some *global* issues inside a big program like GCC. [I would probably agree with the fact that Ggc might not be good enough and need improvements, but most GCC people don't think this way, and try to avoid Ggc. And improving Ggc probably requires the cooperation of the entire GCC commnity, because it impacts the way people will code inside GCC.]. Cheers. -- Basile STARYNKEVITCH http://starynkevitch.net/Basile/ email: basilestarynkevitchnet mobile: +33 6 8501 2359 8, rue de la Faiencerie, 92340 Bourg La Reine, France *** opinions {are only mine, sont seulement les miennes} ***