From owner-freebsd-amd64@FreeBSD.ORG Sat Jul 3 21:13:48 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 74E8416A4CE; Sat, 3 Jul 2004 21:13:48 +0000 (GMT) Received: from mail.mcneil.com (rrcs-west-24-199-45-54.biz.rr.com [24.199.45.54]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5357243D45; Sat, 3 Jul 2004 21:13:46 +0000 (GMT) (envelope-from sean@mcneil.com) Received: from localhost (localhost.mcneil.com [127.0.0.1]) by mail.mcneil.com (Postfix) with ESMTP id E2FB7FD03A; Sat, 3 Jul 2004 14:13:45 -0700 (PDT) Received: from mail.mcneil.com ([127.0.0.1]) by localhost (server.mcneil.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 60301-02; Sat, 3 Jul 2004 14:13:38 -0700 (PDT) Received: from [24.199.45.54] (mcneil.com [24.199.45.54]) by mail.mcneil.com (Postfix) with ESMTP id 2DA14FD012; Sat, 3 Jul 2004 14:13:38 -0700 (PDT) From: Sean McNeil To: Gerald Pfeifer In-Reply-To: References: <200406282008.i5SK88kW075936@peedub.jennejohn.org> <1088472821.3510.3.camel@server.mcneil.com> Content-Type: text/plain Message-Id: <1088889217.60619.10.camel@server.mcneil.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Sat, 03 Jul 2004 14:13:37 -0700 Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at mcneil.com cc: amd64@FreeBSD.org cc: ports@FreeBSD.org Subject: Re: several messages (regarding gcc) X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Jul 2004 21:13:48 -0000 On Sat, 2004-07-03 at 13:41, Gerald Pfeifer wrote: > 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. Yes, I'm sorry for not qualifying that statement: gcc 3.3 ports has poor amd64 support. The gcc 3.3 in core FreeBSD has been modified by the persons mentioned so that it is very stable on amd64. As you say, gcc 3.4 has much better amd64 support and closer ANSI compliance. Because of this, I have found a few packages in ports that will not compile with the gcc 3.4 port (CC=gcc34, CXX=g++34). These tend to be trivial fixes. The only concern I have is that gcc 3.4 produced a non-working openldap-sasl-server-2.1.30. The compiler in core -CURRENT made a functional one. Cheers, Sean