From owner-freebsd-current  Fri Aug  2  1:23:46 2002
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id D8CCB37B400; Fri,  2 Aug 2002 01:23:44 -0700 (PDT)
Received: from snark.rinet.ru (snark.rinet.ru [195.54.192.73])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 84CCA43E4A; Fri,  2 Aug 2002 01:23:43 -0700 (PDT)
	(envelope-from andrew@snark.rinet.ru)
Received: from snark.rinet.ru (andrew@localhost [127.0.0.1])
	by snark.rinet.ru (8.12.3/8.12.3) with ESMTP id g728Najd014340;
	Fri, 2 Aug 2002 12:23:37 +0400 (MSD)
	(envelope-from andrew@snark.rinet.ru)
Received: (from andrew@localhost)
	by snark.rinet.ru (8.12.3/8.12.3/Submit) id g728NaJA014339;
	Fri, 2 Aug 2002 12:23:36 +0400 (MSD)
Date: Fri, 2 Aug 2002 12:23:36 +0400
From: Andrew Kolchoogin <andrew@snark.rinet.ru>
To: "David O'Brien" <obrien@FreeBSD.ORG>
Cc: current@FreeBSD.ORG
Subject: Re: Comments on Release Building for -current
Message-ID: <20020802082336.GA12034@snark.rinet.ru>
References: <20020801173513.GC82778@dragon.nuxi.com> <20020802041414.A3616-100000@gamplex.bde.org> <20020802073955.GA88247@dragon.nuxi.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20020802073955.GA88247@dragon.nuxi.com>
User-Agent: Mutt/1.5.1i
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-current.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-current>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-current>
X-Loop: FreeBSD.ORG

David,

On Fri, Aug 02, 2002 at 12:39:55AM -0700, David O'Brien wrote:

> The rest of the GCC using world can use -O2 on their code.  We are the
> only ones that have so much trouble with it.  It is probably due to our
> bugs, not GCC's.
sorry, but some time ago I read here that gcc -O2 breaks our printf() in
libc. I haven't find any assembler code in /usr/src/lib/libc/stdio/vfprintf.c,
as such, if some C compiler can't handle VALID and STANDARDS-COMPLIANT C code,
this compiler is broken. Isn't it?

Indeed, all of FreeBSD users could help to catch such a bug in gcc optimizer
code. :)

Andrew.

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message