Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 29 May 2007 14:44:53 -0400
From:      Kris Kennaway <kris@obsecurity.org>
To:        Doug Barton <dougb@FreeBSD.org>
Cc:        freebsd-hackers@freebsd.org, Ali Mashtizadeh <mashtizadeh@gmail.com>, freebsd-current@freebsd.org, Alex Dupre <ale@FreeBSD.org>
Subject:   Re: Xorg port problem?
Message-ID:  <20070529184452.GA48484@rot13.obsecurity.org>
In-Reply-To: <465BD140.20504@FreeBSD.org>
References:  <440b3e930705282241u44fa03a8gb0fedbb1617518df@mail.gmail.com> <465BC3A4.7030008@FreeBSD.org> <465BC507.1060902@FreeBSD.org> <465BD140.20504@FreeBSD.org>

next in thread | previous in thread | raw e-mail | index | archive | help

--DocE+STaALJfprDB
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Tue, May 29, 2007 at 12:07:44AM -0700, Doug Barton wrote:
> 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.
> >=20
> > It's the well-known problem of new gcc 4.2 optimizations (bug). Simply
> > compile with -O0 instead of -O2.
>=20
> 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 ...

It wants to use ${BIGNUM} amount of memory to optimize a huge C file,
so that might be fatal (or just terminally irritating) on smaller
systems.

Kris
--DocE+STaALJfprDB
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.3 (FreeBSD)

iD8DBQFGXHSkWry0BWjoQKURAqOAAJwLB0XknNO5MDikrIYZfzPYrxEinwCeJUIL
dw0VatqZb5TFQUC+8YBgREo=
=9odR
-----END PGP SIGNATURE-----

--DocE+STaALJfprDB--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070529184452.GA48484>