Date: Mon, 17 Jan 2005 14:48:09 -0800 From: Kris Kennaway <kris@obsecurity.org> To: Mike Tancsa <mike@sentex.net>, freebsd-stable@freebsd.org Subject: Re: CFLAGS=-O2 -pipe problems in RELENG_5 ? Message-ID: <20050117224809.GC31463@xor.obsecurity.org> In-Reply-To: <20050117193844.GB1110@galgenberg.net> References: <6.2.0.14.0.20050112173437.089758a0@64.7.153.2> <20050113225145.GA781@galgenberg.net> <6.2.0.14.0.20050113193132.042966c8@64.7.153.2> <20050117193844.GB1110@galgenberg.net>
next in thread | previous in thread | raw e-mail | index | archive | help
--IpbVkmxF4tDyP/Kb Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Jan 17, 2005 at 08:38:44PM +0100, Ulrich Spoerlein wrote: > On Thu, 13.01.2005 at 19:38:27 -0500, Mike Tancsa wrote: > > >I'm using -Os -pipe ever since installing 5.x after the gcc update. > > >Haven't encountered any problem so far.. > > There are some differences between O2 and Os according to the man=20 > > page. Are you using that on your kernel and for buildworld ? >=20 > Both, that is everything. Kernel, World, Ports. (Guess I'm lucky) Yes, it's certainly not supported to build ports with -O2 and many are known to have broken code exposed by this setting. > > I let the box run over night building world 8 times with -j2 through -j= 5=20 > > and all worked just fine. >=20 > Ok, that should put hardware out of the question. >=20 > Sorry, no more ideas, besides getting rid of CPUTYPE as that is know to > cause problems. Well, not in general, but in certain isolated cases. Kris --IpbVkmxF4tDyP/Kb Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQFB7ECpWry0BWjoQKURAhAMAKCLdpGY7e5WyPwWOtL6Ec/H6al2+wCfQ3EA f8lcdny5T8khHM8UHiMStg8= =jcJi -----END PGP SIGNATURE----- --IpbVkmxF4tDyP/Kb--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050117224809.GC31463>