From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21016 invoked by alias); 20 Oct 2011 12:10:23 -0000 Received: (qmail 21006 invoked by uid 22791); 20 Oct 2011 12:10:21 -0000 X-SWARE-Spam-Status: No, hits=-6.9 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_HI,RP_MATCHES_RCVD,SPF_HELO_PASS X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 20 Oct 2011 12:09:59 +0000 Received: from int-mx01.intmail.prod.int.phx2.redhat.com (int-mx01.intmail.prod.int.phx2.redhat.com [10.5.11.11]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id p9KC9w8K015240 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Thu, 20 Oct 2011 08:09:58 -0400 Received: from zebedee.pink (ovpn-113-55.phx2.redhat.com [10.3.113.55]) by int-mx01.intmail.prod.int.phx2.redhat.com (8.13.8/8.13.8) with ESMTP id p9KC9vM2015139; Thu, 20 Oct 2011 08:09:57 -0400 Message-ID: <4EA00F94.2030603@redhat.com> Date: Thu, 20 Oct 2011 12:51:00 -0000 From: Andrew Haley User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.23) Gecko/20110928 Fedora/3.1.15-1.fc14 Thunderbird/3.1.15 MIME-Version: 1.0 To: gcc@gcc.gnu.org Subject: Re: adding destroyable objects into Ggc References: <20111018171201.361304028ab94f102f827bd2@starynkevitch.net> <20111018191350.470cd6b1cd291373d5ff3f2c@starynkevitch.net> <20111019135602.GA19325@ours.starynkevitch.net> <20111020115652.GA14705@ours.starynkevitch.net> In-Reply-To: <20111020115652.GA14705@ours.starynkevitch.net> Content-Type: text/plain; charset=ISO-8859-1 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/msg00345.txt.bz2 On 10/20/2011 12:56 PM, Basile Starynkevitch wrote: > So, I am trying to add finalized objects in Ggc not for MELT (it does not > need them, and it already has some finalization tricks which I could use > when some GCC begins to use C++ objects), but for general use For what general use? Surely you're not proposing to add a feature for which you have no use. Andrew.