From owner-freebsd-current@FreeBSD.ORG Wed May 21 18:44:59 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 8489037B401 for ; Wed, 21 May 2003 18:44:59 -0700 (PDT) Received: from mail.pcnet.com (mail.pcnet.com [204.213.232.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id C0CC743F75 for ; Wed, 21 May 2003 18:44:58 -0700 (PDT) (envelope-from eischen@pcnet1.pcnet.com) Received: from pcnet1.pcnet.com (localhost [127.0.0.1]) by mail.pcnet.com (8.12.8/8.12.1) with ESMTP id h4M1ivwQ019525; Wed, 21 May 2003 21:44:57 -0400 (EDT) Received: from localhost (eischen@localhost)h4M1ivdT019518; Wed, 21 May 2003 21:44:57 -0400 (EDT) Date: Wed, 21 May 2003 21:44:57 -0400 (EDT) From: Daniel Eischen To: Jeremy Messenger In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: Jon Lido cc: freebsd-current@freebsd.org 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 01:44:59 -0000 On Wed, 21 May 2003, Jeremy Messenger wrote: > On Wed, 21 May 2003 18:10:14 -0700, David O'Brien > wrote: [ snip ] > > 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. > > Perhaps, it should be add in the errata? Also, add the comments in the > make.conf. > > Cheers, > Mezz > > >> 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. Why do we set CPUTYPE by default? This has bit me before also. It seems to me that NO_CPU_CFLAGS=yes should be the default. Even -mpentiumpro caused problems for me. -- Dan Eischen