-O2 compiler bug on amd64? (Re: new TCL vs. current-6)

[Alexander Leidinger]

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.

-- 
http://www.Leidinger.net/     Alexander @ Leidinger.net: PGP ID = B0063FE7
http://www.FreeBSD.org/        netchild @ FreeBSD.org  : PGP ID = 72077137