From owner-freebsd-current@FreeBSD.ORG Thu May 22 07:11:02 2003 Return-Path: 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 B596D37B404; Thu, 22 May 2003 07:11:02 -0700 (PDT) Received: from lennier.cc.vt.edu (lennier.cc.vt.edu [198.82.162.213]) by mx1.FreeBSD.org (Postfix) with ESMTP id 038BF43FBF; Thu, 22 May 2003 07:11:02 -0700 (PDT) (envelope-from jlido@goof.com) Received: from vivi.cc.vt.edu (IDENT:mirapoint@vivi-lb.cc.vt.edu [10.1.1.12]) by lennier.cc.vt.edu (8.12.8/8.12.8) with ESMTP id h4MEB1qW511486; Thu, 22 May 2003 10:11:01 -0400 (EDT) Received: from hc652a885.dhcp.vt.edu (hc652a885.dhcp.vt.edu [198.82.168.133]) by vivi.cc.vt.edu (Mirapoint Messaging Server MOS 3.3.2-CR) with ESMTP id BEK13251; Thu, 22 May 2003 10:11:00 -0400 (EDT) From: Jon Lido To: freebsd-current@FreeBSD.ORG, "David O'Brien" Date: Thu, 22 May 2003 10:10:59 -0400 User-Agent: KMail/1.5.1 References: <200305201025.30296.jlido@goof.com> <200305201512.27174.jlido@goof.com> <20030522011014.GC27806@dragon.nuxi.com> In-Reply-To: <20030522011014.GC27806@dragon.nuxi.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200305221010.59718.jlido@goof.com> Subject: Re: gcc/libm floating-point bug? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 May 2003 14:11:03 -0000 On Wednesday 21 May 2003 09:10 pm, David O'Brien wrote: > On Tue, May 20, 2003 at 03:12:27PM -0400, Jon Lido wrote: > > Yes, this was the problem. I rebuilt world with -march=pentium3 and that > > did the trick. > > Honest question of you -- I'll assume you're subscribed to > freebsd-current@. How have you missed all the warnings from myself and > others not to trust the -march=pentium4 optimizations? I honestly want > to know so we can figure out a better way of getting the word out. I missed it in the volume of email on freebsd-current. When I started using -current almost two weeks ago now, I browsed about a month's worth of the mailing list archives. I searched on gcc and libm in the list archives, but I didn't really connect the rambling discussions with the problem I was seeing. I admit that, in hindsight, it should have been pretty obvious. > > I'm not sure how CPUTYPE gets handled, but perhaps p4 should expand to > > -march=pentium3, if possible. > > I feel some will screem if we take away the ability to use > -march=pentium4 in places they know for sure will work. Unix is about > mechanisms, not policy. Well, we've got a compiler here with a broken mechanism. Deciding whether or not to act on it sounds like a policy decision to me. I just hope 5.1 doesn't get shipped with such an easy way to break stuff. -Jon