From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8345 invoked by alias); 30 Apr 2005 19:33:28 -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 8336 invoked from network); 30 Apr 2005 19:33:24 -0000 Received: from unknown (HELO smtp20.libero.it) (193.70.192.147) by sourceware.org with SMTP; 30 Apr 2005 19:33:24 -0000 Received: from localhost (172.16.1.82) by smtp20.libero.it (7.0.027-DD01) id 41D02C9801AF02F9; Sat, 30 Apr 2005 21:33:22 +0200 Received: from bagio (151.41.176.36) by smtp20.libero.it (7.0.027-DD01) id 41D02BD305CC877A; Sat, 30 Apr 2005 21:33:21 +0200 Received: from 127.0.0.1 (AVG SMTP 7.0.308 [266.10.4]); Sat, 30 Apr 2005 21:33:23 +0200 Message-ID: <027601c54dbb$79159d90$24b02997@bagio> From: "Giovanni Bajo" To: "Ian Lance Taylor" , Cc: "David Edelsohn" , "Jason Thorpe" References: <426F2D5D.7010305@3am-software.com><200504271441.j3REfND27584@makai.watson.ibm.com><43D7D183-F9AF-4728-8564-8A6C74673E3E@shagadelic.org> Subject: Re: GCC 4.1: Buildable on GHz machines only? Date: Sat, 30 Apr 2005 19:40:00 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-SW-Source: 2005-04/txt/msg01743.txt.bz2 Ian Lance Taylor wrote: >> Except it's not just bootstrapping GCC. It's everything. When the >> NetBSD Project switched from 2.95.3 to 3.3, we had a noticeably >> increase in time to do the "daily" builds because the 3.3 compiler >> was so much slower at compiling the same OS source code. And we're >> talking almost entirely C code, here. > > Well, there are two different issues. Matt was originally talking > about bootstrap time, at least that is how I took it. You are talking > about speed of compilation. The issues are not unrelated, but they > are not the same. > > The gcc developers have done a lot of work on speeding up the compiler > for 3.4 and 4.0, with some success. On many specific test cases, 4.0 > is faster than 3.3 and even 2.95. The way to help this process along > is to report bugs at http://gcc.gnu.org/bugzilla. > > In particular, if you provide a set of preprocessed .i files, from, > say, sys, libc, or libcrypto, whichever seems worst, and open a gcc PR > about them, that would be a great baseline for measuring speed of > compilation, in a way that particularly matters to NetBSD developers. I would also like to note that I *myself* requested preprocessed source code to NetBSD developers at least 6 times in the past 2 years. I am sure Andrew Pinski did too, a comparable amound of times. These requests, as far as I can understand, were never answered. This also helped building up a stereotype of the average NetBSD developer being "just a GCC whine troll". I am sure this is *far* from true, but I would love to see NetBSD developers *collaborating* with us, especially since what we are asking (filing bug reports with preprocessed sources) cannot take more than 1-2 hours of their time. Giovanni Bajo