Date: Tue, 14 Dec 2004 13:39:58 +0100 From: Alexander Leidinger <Alexander@Leidinger.net> To: Kris Kennaway <kris@obsecurity.org> Cc: ade@freebsd.org Subject: Re: -O2 compiler bug on amd64? (Re: new TCL vs. current-6) Message-ID: <1103027998.41bedf1e46fa1@netchild.homeip.net> In-Reply-To: <20041214062738.GA78138@xor.obsecurity.org> References: <200412081205.39354.mi%2Bmx@aldan.algebra.com> <20041208171947.GA46271@xor.obsecurity.org> <20041214062738.GA78138@xor.obsecurity.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Zitat von Kris Kennaway <kris@obsecurity.org>: > > Peter speculated a problem when the world is built with -O2 (with or > > without -fno-strict-aliasing). I haven't been able to confirm this by > > testing with a world built with -O, because I only have one working > > amd64 package builder. > > Looks like building the port against an -O world has fixed the > problems. This suggests a compiler bug with -O2 on amd64. I "hope" this is the case, not only on amd64. Background: I see coredumps of gst-register on my system (x86). I've recompiled all ports, with and without -Os, with and without -fno-strict-aliasing, but it still segfaults. I also recompiled world with "-Os -fno-strict-aliasing" instead of my usual "-Os". I haven't tested plain "-O" for the world yet, but I think the problem is somewhere in the system libs... Bye, Alexander. -- http://www.Leidinger.net/ Alexander @ Leidinger.net: PGP ID = B0063FE7 http://www.FreeBSD.org/ netchild @ FreeBSD.org : PGP ID = 72077137
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1103027998.41bedf1e46fa1>