Date: Tue, 29 May 2007 00:07:44 -0700 From: Doug Barton <dougb@FreeBSD.org> To: Alex Dupre <ale@FreeBSD.org> Cc: freebsd-hackers@freebsd.org, Ali Mashtizadeh <mashtizadeh@gmail.com>, freebsd-current@freebsd.org Subject: Re: Xorg port problem? Message-ID: <465BD140.20504@FreeBSD.org> In-Reply-To: <465BC507.1060902@FreeBSD.org> References: <440b3e930705282241u44fa03a8gb0fedbb1617518df@mail.gmail.com> <465BC3A4.7030008@FreeBSD.org> <465BC507.1060902@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Alex Dupre wrote:
> Doug Barton wrote:
>>> (Over 2GBs of RAM + Swap being used). It does this consistently when it
>>> tries to compile xf86PciScan.c (hope thats the right file).
>> May not be the answer you want to hear, but I built all the xorg stuff
>> multiple times on -current systems both pre and post the gcc + symver
>> + version bump eras, and didn't have the problems you're seeing.
>
> It's the well-known problem of new gcc 4.2 optimizations (bug). Simply
> compile with -O0 instead of -O2.
Not disputing your answer, but I'm curious. Why would it cause
problems on some systems but not others? I haven't done anything with
my cflags ...
Doug
--
This .signature sanitized for your protection
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?465BD140.20504>