From owner-freebsd-current@FreeBSD.ORG Mon Jun 18 19:39:05 2007 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id CA4A616A400 for ; Mon, 18 Jun 2007 19:39:05 +0000 (UTC) (envelope-from youshi10@u.washington.edu) Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mx1.freebsd.org (Postfix) with ESMTP id A983513C44B for ; Mon, 18 Jun 2007 19:39:05 +0000 (UTC) (envelope-from youshi10@u.washington.edu) Received: from hymn01.u.washington.edu (hymn01.u.washington.edu [140.142.8.55]) by mxout2.cac.washington.edu (8.13.7+UW06.06/8.13.7+UW07.05) with ESMTP id l5IJd45h002488 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Mon, 18 Jun 2007 12:39:05 -0700 Received: from localhost (localhost [127.0.0.1]) by hymn01.u.washington.edu (8.13.7+UW06.06/8.13.7+UW07.03) with ESMTP id l5IJd4IE002714 for ; Mon, 18 Jun 2007 12:39:04 -0700 X-Auth-Received: from [192.55.52.1] by hymn01.u.washington.edu via HTTP; Mon, 18 Jun 2007 12:39:04 PDT Date: Mon, 18 Jun 2007 12:39:04 -0700 (PDT) From: youshi10@u.washington.edu To: current@freebsd.org In-Reply-To: <20070618170641.GB73978@rot13.obsecurity.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-PMX-Version: 5.3.1.294258, Antispam-Engine: 2.5.1.298604, Antispam-Data: 2007.6.18.122134 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='NO_REAL_NAME 0, __CP_URI_IN_BODY 0, __CT 0, __CT_TEXT_PLAIN 0, __FRAUD_419_BADTHINGS 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0' Cc: Subject: Re: [AMD64] X.org build eats all the memory when compiled with GCC 4.2 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Jun 2007 19:39:05 -0000 On Mon, 18 Jun 2007, Kris Kennaway wrote: > On Mon, Jun 18, 2007 at 08:40:30AM -0400, Daniel Eischen wrote: >> On Mon, 18 Jun 2007, Michiel Boland wrote: >> >>> On Sat, 16 Jun 2007, Garrett Cooper wrote: >>> >>>> Claus Guttesen wrote: >>>>>> I recompiled X.org yesterday and hit the following problem >>>>>> (1 week old -current, yesterdays packages, AMD64) -- when compiling >>>>>> files in >>>>>> /usr/ports/x11-servers/xorg-server/work/xorg-server-1.2.0/hw/xfree86/scanpci >>>>>> directory, there are huge .h files - about 4mb. when compiler uses -O2 >>>>>> or -O option it eats all available memory and then gets killed by the >>>>>> system. >>>>>> Without -O/O2 option compile works just as expected. >>>>>> >>>>>> Now -- should I file a PR or it's known bug? >>>>> >>>>> No, but you should read the archives. Requires more than 1 GB of swap. >>>>> >>>> It's a known bug that isn't going to be fixed until gcc 4.2.1. >>>> -Garrett >>>> >>> >>> Well, until then, is it not possible to at least put the following patch >>> in ports/x11-servers/xorg-server/files: >> >> [ ... ] >> >>> That would make a lot of people very happy. In particular those running >>> amd64. >> >> Yes, it happens on i386 too. I think requiring more than 1GB of swap >> is ridiculous. Please patch gcc or the port. > > You can test the new gcc snapshot here: > > http://people.freebsd.org/~kan/contrib-gcc421.tar.gz > > Just extract it over the top of /usr/src and rebuild world. Please > confirm that it helps with this problem. > > Kris Ok, I'll give it a shot on my i386 and amd64 boxes when I get back home tonight. FYI, from : I would like to try to keep the GCC 4.2.x release branch on the time-driven release cycle for point releases that is part of the GCC development plan. I left an embarrassing gap in the GCC 4.1.x release cycle, and I plan to avoid that mistake for GCC 4.2.x. Therefore, I plan to make the GCC 4.2.1 release on or about July 13th. As with the 4.2.0 release, I will be most concerned about P1 regressions in 4.2.x, not present in 4.1.x. So the next release is just around the corner. Yay! Cheers, -Garrett