From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9065 invoked by alias); 27 Jun 2009 13:41:37 -0000 Received: (qmail 9057 invoked by uid 22791); 27 Jun 2009 13:41:37 -0000 X-SWARE-Spam-Status: No, hits=-2.5 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from rock.gnat.com (HELO rock.gnat.com) (205.232.38.15) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Sat, 27 Jun 2009 13:41:29 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by filtered-rock.gnat.com (Postfix) with ESMTP id DEBB52BAB32; Sat, 27 Jun 2009 09:41:27 -0400 (EDT) Received: from rock.gnat.com ([127.0.0.1]) by localhost (rock.gnat.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id vvxGwPsgSmI1; Sat, 27 Jun 2009 09:41:27 -0400 (EDT) Received: from [127.0.0.1] (nile.gnat.com [205.232.38.5]) by rock.gnat.com (Postfix) with ESMTP id 8AA6F2BAB0A; Sat, 27 Jun 2009 09:41:27 -0400 (EDT) Message-ID: <4A462182.40608@adacore.com> Date: Sat, 27 Jun 2009 15:19:00 -0000 From: Robert Dewar User-Agent: Thunderbird 2.0.0.22 (Windows/20090605) MIME-Version: 1.0 To: Daniel Berlin CC: Richard Guenther , Ian Lance Taylor , Matt , gcc@gcc.gnu.org Subject: Re: Phase 1 of gcc-in-cxx now complete References: <84fc9c000906270248y481a5ab5i674ac61b71cf4f87@mail.gmail.com> <4aca3dc20906270639g5161e516kda973e8c683948@mail.gmail.com> In-Reply-To: <4aca3dc20906270639g5161e516kda973e8c683948@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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: 2009-06/txt/msg00639.txt.bz2 Daniel Berlin wrote: >> All that above said - do you expect us to carry both vec.h (for VEC in >> GC memory) and std::vector (for VECs in heap memory) (and vec.h >> for the alloca trick ...)? Or do you think we should try to make the GTY >> machinery C++ aware and annotate the standard library (ick...)? > > Since the containers have mostly standard iterators, i'm not sure we > have to do much to the standard library. Simply require a set of > iterators with the right properties exist and generate code that > depends on this. > If you make your own container, you have to implement the iterators. Shouldn't this be a new thread, or is this really part of phase 1?