From owner-freebsd-current@FreeBSD.ORG Tue Aug 19 08:28:07 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 727B416A4C0 for ; Tue, 19 Aug 2003 08:28:07 -0700 (PDT) Received: from alpha.siliconlandmark.com (alpha.siliconlandmark.com [209.69.98.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 31F9243F3F for ; Tue, 19 Aug 2003 08:28:06 -0700 (PDT) (envelope-from andy@siliconlandmark.com) Received: from alpha.siliconlandmark.com (localhost [127.0.0.1]) h7JFS53E002089; Tue, 19 Aug 2003 11:28:05 -0400 (EDT) (envelope-from andy@siliconlandmark.com) Received: from localhost (andy@localhost)h7JFS5TC002086; Tue, 19 Aug 2003 11:28:05 -0400 (EDT) (envelope-from andy@siliconlandmark.com) X-Authentication-Warning: alpha.siliconlandmark.com: andy owned process doing -bs Date: Tue, 19 Aug 2003 11:28:05 -0400 (EDT) From: Andre Guibert de Bruet To: Stefan Bethke In-Reply-To: <844382971.1061287624@[10.0.1.3]> Message-ID: <20030819112619.S452@alpha.siliconlandmark.com> References: <2147483647.1061141322@[172.22.33.128]> <20030818030054.GA58513@dragon.nuxi.com> <844382971.1061287624@[10.0.1.3]> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-current@freebsd.org Subject: Re: CPUTYPE considered harmful? (was: Lot's of SIGILL, SIGSEGV) 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: Tue, 19 Aug 2003 15:28:07 -0000 On Tue, 19 Aug 2003, Stefan Bethke wrote: > On Montag, 18. August 2003 23:15 Uhr +0200 Pawel Jakub Dawidek > wrote: > > > On Sun, Aug 17, 2003 at 08:00:54PM -0700, David O'Brien wrote: > > +> > This is a FAQ. In the future, please search the archives before > > posting. +> > > > +> > At this moment in time, 'p4' isn't a safe CPUTYPE (It produces broken > > +> > code). 'p3' or 'i686' are what's recommended for Pentium 4s. > > +> > > +> Andre, I think you are out of date -- CPUTYPE=p4 is now safe with GCC > > +> 3.3.1. > > > > I think he is right, because when upgrading host where was gcc3.2 to > > current -CURRENT (with gcc3.3) 'make world' builds make(1) in first > > place and it is builded by gcc3.2 with CPUTYPE=p4, so it will be broken. > > > > So gcc have to be upgraded in first place (with CPUTYPE=p3). > > Hhm, sounds reasonable. > > However, I had the exact same problem updating from a 5.1-RC to a recent > current on a P III 900, and there, I had CPUTYPE=p3 in make.conf. > > Removing CPUTYPE eventually gave me back working systems (I did restore > 5.1-R bits prior to make world). Unfortunatly, I don't have the resources > to investigate this further, but for the time being, I will not use CPUTYPE > until others can confirm it's safe :-) I've been running my laptop with a world that was built with CPUTYPE=p3 (GCC 3.3.1) for close to a month. I haven't noticed anything odd yet. Regards, > Andre Guibert de Bruet | Enterprise Software Consultant > > Silicon Landmark, LLC. | http://siliconlandmark.com/ >