From owner-freebsd-amd64@FreeBSD.ORG Tue Jun 29 01:33:50 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 A2DBC16A50A; Tue, 29 Jun 2004 01:33:44 +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 41C1743D54; Tue, 29 Jun 2004 01:33:42 +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 CABDFFD087; Mon, 28 Jun 2004 18:33:41 -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 71698-07; Mon, 28 Jun 2004 18:33:41 -0700 (PDT) Received: from [24.199.45.54] (mcneil.com [24.199.45.54]) by mail.mcneil.com (Postfix) with ESMTP id 49113FD07B; Mon, 28 Jun 2004 18:33:41 -0700 (PDT) From: Sean McNeil To: Gary Jennejohn In-Reply-To: <200406282008.i5SK88kW075936@peedub.jennejohn.org> References: <200406282008.i5SK88kW075936@peedub.jennejohn.org> Content-Type: text/plain Message-Id: <1088472821.3510.3.camel@server.mcneil.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Mon, 28 Jun 2004 18:33:41 -0700 Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at mcneil.com cc: amd64@FreeBSD.org cc: ports@FreeBSD.org cc: Gerald Pfeifer Subject: Re: gcc33 and amd64 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: Tue, 29 Jun 2004 01:33:50 -0000 On Mon, 2004-06-28 at 13:08, Gary Jennejohn wrote: > Gerald Pfeifer writes: > > The gcc33 port keeps failing on our amd64 target, yet I have not seen > > any report on the gcc mailing lists. > > > > I don't have any amd64 box with FreeBSD available -- could someone please > > try to build this port to rule out hardware issues in our build cluster? > > > > Another possibility might be that our system compiler is broken and > > miscompiles gcc33 on this platform. You should be able to test this > > by installing the gcc34 port and then setting CC to gcc34. > > > > Any volunteers to help me with that? Any further ideas? > > > > stage1/xgcc -Bstage1/ -B/usr/local/x86_64-portbld-freebsd5.2/bin/ -g -O2 -D > > IN_GCC -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -W > > traditional -pedantic -Wno-long-long -DHAVE_CONFIG_H -DGENERATOR_FILE -o g > > engtype \ > > gengtype.o gengtype-lex.o gengtype-yacc.o ../libiberty/libiberty.a > > ./gengtype > > gmake[2]: *** [s-gtype] Bus error (core dumped) > > gmake[2]: Leaving directory `/tmp/a/ports/lang/gcc33/work/build/gcc' > > gmake[1]: *** [stage2_build] Error 2 > > gmake[1]: Leaving directory `/tmp/a/ports/lang/gcc33/work/build/gcc' > > gmake: *** [bootstrap-lean] Error 2 > > *** Error code 2 > > > > 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 > > In 64bit mode I also see scads of ``ASM_OUTPUT_MAX_SKIP_ALIGN redefined'' > warnings. I didn't watch the 32bit build closely enough to notice > whether it also emits these warnings. 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. Sean