Le Mardi 14 décembre 2004 à 13:39 +0100, Alexander Leidinger a écrit : > Zitat von Kris Kennaway <kris_at_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. Some more information : gst-register coredumps if gstreamer-plugins is compiled with CPUTYPE=p4. eclipse also coredumps if gtk2 is compiled with CPUTYPE=p4. Both ports don't depend on optimization level (-O2 or -O). Anthony.Received on Tue Dec 14 2004 - 12:24:56 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:38:24 UTC