From owner-freebsd-current Fri Aug 9 7:57: 5 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 2DCA037B400; Fri, 9 Aug 2002 07:57:01 -0700 (PDT) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id 882A243E86; Fri, 9 Aug 2002 07:57:00 -0700 (PDT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.12.5/8.12.5) id g79EurZh048978; Fri, 9 Aug 2002 09:56:53 -0500 (CDT) (envelope-from dan) Date: Fri, 9 Aug 2002 09:56:52 -0500 From: Dan Nelson To: current@FreeBSD.ORG Cc: Bruce Evans , Mike Barcroft , Andrew Kolchoogin Subject: Re: Comments on Release Building for -current Message-ID: <20020809145652.GB3773@dan.emsphone.com> References: <20020803123249.B70372@espresso.q9media.com> <20020804195905.O1075-100000@gamplex.bde.org> <20020809044652.GA12216@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020809044652.GA12216@dragon.nuxi.com> X-OS: FreeBSD 5.0-CURRENT X-message-flag: Outlook Error User-Agent: Mutt/1.5.1i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In the last episode (Aug 08), David O'Brien said: > On Sun, Aug 04, 2002 at 08:01:10PM +1000, Bruce Evans wrote: > > > > 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, > ... > > > 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. > > It looks like this PR is against the system GCC 3.1. As such it > isn't a very interesting bug report. Someone needs to test to see if > this bug exists when using the gcc31 (gcc 3.1.1 release) port. It does. -- Dan Nelson dnelson@allantgroup.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message