From owner-freebsd-stable@FreeBSD.ORG  Thu Jun  9 19:31:46 2005
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
X-Original-To: freebsd-stable@freebsd.org
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id B05EF16A41C
	for <freebsd-stable@freebsd.org>; Thu,  9 Jun 2005 19:31:46 +0000 (GMT)
	(envelope-from jkim@niksun.com)
Received: from anuket.mj.niksun.com (gwnew.niksun.com [65.115.46.162])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 61A9443D48
	for <freebsd-stable@freebsd.org>; Thu,  9 Jun 2005 19:31:43 +0000 (GMT)
	(envelope-from jkim@niksun.com)
Received: from [10.70.0.244] (daemon.mj.niksun.com [10.70.0.244])
	by anuket.mj.niksun.com (8.13.1/8.13.1) with ESMTP id j59JW2fI018606;
	Thu, 9 Jun 2005 15:32:03 -0400 (EDT) (envelope-from jkim@niksun.com)
From: Jung-uk Kim <jkim@niksun.com>
Organization: Niksun, Inc.
To: freebsd-stable@freebsd.org
Date: Thu, 9 Jun 2005 15:31:30 -0400
User-Agent: KMail/1.6.2
References: <E1DgKLF-0007mu-W9@dilbert.firstcallgroup.co.uk>
In-Reply-To: <E1DgKLF-0007mu-W9@dilbert.firstcallgroup.co.uk>
MIME-Version: 1.0
Content-Disposition: inline
Content-Type: text/plain;
  charset="euc-kr"
Content-Transfer-Encoding: 7bit
Message-Id: <200506091531.30443.jkim@niksun.com>
X-Virus-Scanned: ClamAV version 0.85.1,
	clamav-milter version 0.85 on anuket.mj.niksun.com
X-Virus-Status: Clean
Cc: david@fundamentalit.com, jhs@flat.berklix.net,
	Pete French <petefrench@ticketswitch.com>
Subject: Re: FreeBSD 5.4: Is it generally unstable?GCC broken for amd64 ?
	(was Re: FreeBSD 5.4: Is it generally unstable?)
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, 
	<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Jun 2005 19:31:46 -0000

On Thursday 09 June 2005 06:32 am, Pete French wrote:
> > "Julian H. Stacey" <jhs@flat.berklix.net> writes:
> > 	GCC 3.4.2 on 5.4-RELEASE has a bug for amd64,
> > 		I started avoiding that by putting
> > 			CFLAGS=              -O0
> > 		in /etc/make.conf
> > 		More info from:
> > 			Message from "David O'Brien" <obrien@freebsd.org>
> > 		of "Thu, 02 Jun 2005 01:26:15 PDT."
> > 			 <20050602082615.GA36096@dragon.NUXI.org>
>
> This worries me a lot, but I have not been able to locate the
> quoted email! (how do you make the archives search on message ID?)

http://docs.freebsd.org/cgi/mid.cgi?20050602082615.GA36096
http://docs.freebsd.org/cgi/mid.cgi?200506011833.12686.jkim

For more info about this issue:
http://docs.freebsd.org/cgi/mid.cgi?IDTR9T00.LMF
http://docs.freebsd.org/cgi/mid.cgi?20050324194817.N97600
http://docs.freebsd.org/cgi/mid.cgi?20050324182524.J97436

> Does anyone have any,more information on this - I'd hate to start
> cmmitting production code to a buggy compiler!

Don't panic; it is not critical at all.  Other critical issues are 
fixed in GCC 3.4.4, which is in -CURRENT.  On -STABLE, you can use 
ports/lang/gcc34 from ports.

Jung-uk Kim

> -pcf.