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

From: Kris Kennaway <kris_at_obsecurity.org>
Date: Mon, 13 Dec 2004 22:27:38 -0800
On Wed, Dec 08, 2004 at 09:19:47AM -0800, Kris Kennaway wrote:
> On Wed, Dec 08, 2004 at 12:05:38PM -0500, Mikhail Teterin wrote:
> > Three of my TCL-based ports fail now on amd64 running current-6. All failures 
> > occur, when an attempt is made to use the TCL-interpreter -- either to run 
> > the port's self-tests, or to generate the manual pages. The failures are 
> > either "Floating point exceptions" or "Segmentation faults" and appear to 
> > only happen on amd64 (may be, on ia64 as well):
> > 
> > http://people.freebsd.org/~fenner/errorlogs/mi%40aldan.algebra.com.html
> > 
> > Can anyone confirm being able to use freshly built TCL on amd64 _at all_?
> > 
> > My ports did not change in months -- what could be wrong with TCL and/or 
> > amd64?
> 
> 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.

Kris




Received on Tue Dec 14 2004 - 05:27:39 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:38:24 UTC