From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 25211 invoked by alias); 14 Jan 2004 19:47:44 -0000 Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org Received: (qmail 25204 invoked from network); 14 Jan 2004 19:47:44 -0000 Received: from unknown (HELO mail-out4.apple.com) (17.254.13.23) by sources.redhat.com with SMTP; 14 Jan 2004 19:47:44 -0000 Received: from mailgate2.apple.com (a17-128-100-204.apple.com [17.128.100.204]) by mail-out4.apple.com (8.12.10/8.12.9) with ESMTP id i0EJlhcb011935 for ; Wed, 14 Jan 2004 11:47:43 -0800 (PST) Received: from relay2.apple.com (relay2.apple.com) by mailgate2.apple.com (Content Technologies SMTPRS 4.3.6) with ESMTP id ; Wed, 14 Jan 2004 11:47:43 -0800 Received: from apple.com (mrs1.apple.com [17.201.24.248]) by relay2.apple.com (8.12.10/8.12.9) with ESMTP id i0EJlgaO017621; Wed, 14 Jan 2004 19:47:42 GMT Date: Wed, 14 Jan 2004 19:47:00 -0000 Subject: Re: gcc 3.5 integration branch proposal Content-Type: text/plain; charset=US-ASCII; format=flowed Mime-Version: 1.0 (Apple Message framework v551) Cc: Daniel Berlin , David Edelsohn , Geoff Keating , Mark Mitchell , gcc@gcc.gnu.org To: Joe Buck From: Mike Stump In-Reply-To: <20040113173551.A23134@synopsys.com> Message-Id: <845BED52-46CA-11D8-BCF6-003065A77310@apple.com> Content-Transfer-Encoding: 7bit X-SW-Source: 2004-01/txt/msg00883.txt.bz2 On Tuesday, January 13, 2004, at 05:35 PM, Joe Buck wrote: > On Tue, Jan 13, 2004 at 03:29:12PM -0800, Mike Stump wrote: >> Along these lines, I'd like to see C++ about 4x faster. I'd be happy >> with 2x faster[1], anything less, well, isn't interesting. I'd like >> for the SC to find and appoint such a person to tackle speed problems. > > Want the job? :-) I'd happy to volunteer... I'd be happy to have others do so as well, I'd be happy to have a couple of people listed... > It's not like there is a paid position available. My position isn't that of Tom Lord, :-) but, what they are in a position to do is to find someone that will volunteer to be the maintainer for compilation speed for C++. Part of that is to ensure that the compiler doesn't regress, part of that is to encourage others to consider compilation speed issues before it regresses, and the largest part would be rolling up the sleeves and doing the work. By appoint, I merely meant bless to be the listed maintainer for such an issue. I think we need more than just a few random people donating a few random patches to be able to approach a 4x speedup. Let us know if such a position is to be created at this time, and who's on the hook for it...