From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27920 invoked by alias); 6 Aug 2014 16:05:00 -0000 Mailing-List: contact gcc-help-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-help-owner@gcc.gnu.org Received: (qmail 27807 invoked by uid 89); 6 Aug 2014 16:04:59 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=1.3 required=5.0 tests=AWL,BAYES_50,FREEMAIL_FROM,KAM_MXURI,RCVD_IN_DNSWL_NONE,RP_MATCHES_RCVD,SPF_PASS autolearn=no version=3.3.2 X-HELO: omr-d03.mx.aol.com Received: from omr-d03.mx.aol.com (HELO omr-d03.mx.aol.com) (205.188.109.200) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES256-SHA encrypted) ESMTPS; Wed, 06 Aug 2014 16:04:58 +0000 Received: from mtaout-mca01.mx.aol.com (mtaout-mca01.mx.aol.com [172.26.221.77]) by omr-d03.mx.aol.com (Outbound Mail Relay) with ESMTP id 607EE702CEE53 for ; Wed, 6 Aug 2014 12:04:56 -0400 (EDT) Received: from [192.168.0.3] (cpe-65-26-156-163.cinci.res.rr.com [65.26.156.163]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by mtaout-mca01.mx.aol.com (MUA/Third Party Client Interface) with ESMTPSA id F1B12380000A3 for ; Wed, 6 Aug 2014 12:04:55 -0400 (EDT) Message-ID: <53E25225.10201@aol.com> Date: Wed, 06 Aug 2014 16:05:00 -0000 From: Tim Prince User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: gcc-help@gcc.gnu.org Subject: Re: Time taken by GCC 4.9.1 to compile References: <53E24A6E.3080102@redhat.com> In-Reply-To: <53E24A6E.3080102@redhat.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit x-aol-global-disposition: G x-aol-sid: 3039ac1add4d53e252270825 X-AOL-IP: 65.26.156.163 X-SW-Source: 2014-08/txt/msg00045.txt.bz2 On 8/6/2014 11:31 AM, Jeff Law wrote: > On 08/05/14 23:49, Syed Ahsan Ali Bokhari wrote: >> I wonder how much time it takes to compile gcc-4.9.1. After "make" 2 >> hours have been passed and still build underway. > It's highly dependent on your processor's speed and how many > processors you have. > > I've got one system here where it takes about a week (no testsuite). > On the systems where I typically do builds it's a couple hours > (testsuite included). I'd bet on David M.'s box it's probably less > than 30 minutes ;) > > Certainly if you have a multi-processor using the "-j #cpus" option to > make will speed things up considerably. > > jeff Nearly 4 hours to build C Fortran C++ on my Win8.1 4-core laptop. (with "prerequisites" pre-installed). That's the worse case I encounter routinely. 8 hours to run testsuite, with each language started in an independent session. There are still occasional spurious time-outs and early aborts. Attempting to run testsuite on faster Windows boxes is counter-productive due to Windows holding files busy. An obsolete linux box here will build and test in well under 2 hours.