Date: Sun, 17 Jun 2007 08:56:22 +0200 From: Roman Divacky <rdivacky@freebsd.org> To: Garrett Cooper <youshi10@u.washington.edu> Cc: Gaspar Chilingarov <casper@web.am>, freebsd-current@freebsd.org, Claus Guttesen <kometen@gmail.com> Subject: Re: [AMD64] X.org build eats all the memory when compiled with GCC 4.2 Message-ID: <20070617065622.GA33155@freebsd.org> In-Reply-To: <467467B7.8060408@u.washington.edu> References: <46745631.7000708@web.am> <b41c75520706161528q650364dp85700b86353d28b7@mail.gmail.com> <467467B7.8060408@u.washington.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Jun 16, 2007 at 03:44:07PM -0700, 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 I also noticed problems with compiling gcc itself on 512M RAM + 1G swap on i386 with -Os (change to -O2 fixed that) could we import the fix from gcc to ship better gcc in 7.0R? roman
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070617065622.GA33155>