From owner-freebsd-current  Sun Aug  4  2:56:15 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 9B16037B400; Sun,  4 Aug 2002 02:56:12 -0700 (PDT)
Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 2601543E5E; Sun,  4 Aug 2002 02:56:11 -0700 (PDT)
	(envelope-from bde@zeta.org.au)
Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102])
	by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id TAA17365;
	Sun, 4 Aug 2002 19:56:09 +1000
Date: Sun, 4 Aug 2002 20:01:10 +1000 (EST)
From: Bruce Evans <bde@zeta.org.au>
X-X-Sender: bde@gamplex.bde.org
To: Mike Barcroft <mike@FreeBSD.ORG>
Cc: Andrew Kolchoogin <andrew@snark.rinet.ru>,
	"David O'Brien" <obrien@FreeBSD.ORG>, <current@FreeBSD.ORG>
Subject: Re: Comments on Release Building for -current
In-Reply-To: <20020803123249.B70372@espresso.q9media.com>
Message-ID: <20020804195905.O1075-100000@gamplex.bde.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
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

On Sat, 3 Aug 2002, Mike Barcroft wrote:

> Andrew Kolchoogin <andrew@snark.rinet.ru> writes:
> > ...
> > 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. :)
>
> If someone could find the small segment of code where the optimizer
> screws up, and write a small program to demonstrate the problem, we
> would have a good chance of it getting fixed.

Er, someone (Dan Lukes) has already done this.  See PR 40209.  I'm sorry
I haven't found time to look at it in detail.

Bruce


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