From owner-freebsd-current@FreeBSD.ORG Mon May 23 02:48:29 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org 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 4460116A41C; Mon, 23 May 2005 02:48:29 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 748DF43D55; Mon, 23 May 2005 02:48:23 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.11] (junior.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.13.3/8.13.3) with ESMTP id j4N2owJ0015754; Sun, 22 May 2005 20:50:58 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <42914448.5020505@samsco.org> Date: Sun, 22 May 2005 20:47:36 -0600 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.5) Gecko/20050218 X-Accept-Language: en-us, en MIME-Version: 1.0 To: obrien@freebsd.org References: <20050518051111.GA33262@Athena.infor.org> <20050520164349.GD6982@dragon.NUXI.org> <428E1815.8080500@samsco.org> <200505221453.44007.peter@wemm.org> <429105D8.6000106@samsco.org> <20050523021527.GA62693@dragon.NUXI.org> In-Reply-To: <20050523021527.GA62693@dragon.NUXI.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-2.8 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on pooker.samsco.org Cc: freebsd-current@freebsd.org, David Gurvich Subject: Re: Newest loader from CVS not working X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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: Mon, 23 May 2005 02:48:29 -0000 David O'Brien wrote: > On Sun, May 22, 2005 at 04:21:12PM -0600, Scott Long wrote: > >>>What I fixed was an amd64 build problem. The thread starter here was >>>talking about pentium-m builds, so I assume its i386 in this case. >> >>Yes, the threads jumped back and forth between people experiencing >>problems with non-default CFLAGS <..snip..> > > > I've heard those problems on and off for a year now - with no one > experiencing the problem spending sufficient effort to provide a decent > analysis of the issue. > Re-read the threads. There is a lot of good analysis on how gcc was emitting SSE instructions. Scott