Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 3 Jul 2004 22:41:09 +0200 (CEST)
From:      Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at>
To:        Gary Jennejohn <garyj@jennejohn.org>, Sean McNeil <sean@mcneil.com>
Cc:        ports@FreeBSD.org
Subject:   Re: several messages
Message-ID:  <Pine.BSF.4.58.0407032238290.24414@acrux.dbai.tuwien.ac.at>
In-Reply-To: <1088472821.3510.3.camel@server.mcneil.com>
References:  <200406282008.i5SK88kW075936@peedub.jennejohn.org> <1088472821.3510.3.camel@server.mcneil.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 28 Jun 2004, Gary Jennejohn wrote:
> On my amd64 box running a freshly cvsup'ed and installed system (world
> and kernel in 32 and 64 bit mode) I see:
>
> 32bit mode - ``make all'' succeeds
> 64bit mode - gentype fails with signal 10, just like you've observed
On Mon, 28 Jun 2004, Sean McNeil wrote:
> This is sort of expected (at least by me).  Support for amd64 is not
> very mature in 3.3 and I've run into several issues with it.  3.4 should
> work a lot better.  Hopefully, 3.4 will be merged into FreeBSD soon.

Thanks for your feedback.  I agree, and thus marked the gcc33 port BROKEN
on amd64:

  Mark BROKEN on amd64.  It looks like the system compiler miscompiles
  this, and most people on this platform will use either the system
  compiler or gcc34 anyways.

There is a very stable variant of GCC 3.3 available on the hammer-branch
in GCC CVS, which got a lot of feeding and caring from David O'Brien and
colleagues plus colleagues of mine (in our respective day jobs), but when
it comes to official GCC releases, it's really 3.4 and later that rock on
amd64.

Gerald
-- 
Gerald "Jerry"   pfeifer@dbai.tuwien.ac.at   http://www.pfeifer.com/gerald/



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.58.0407032238290.24414>