From owner-freebsd-current@FreeBSD.ORG Tue Aug 19 01:07:11 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 E1C0E16A4BF for ; Tue, 19 Aug 2003 01:07:11 -0700 (PDT) Received: from rohrpostix.tallence.de (rohrpostix.tallence.de [212.77.172.77]) by mx1.FreeBSD.org (Postfix) with ESMTP id BBDCB43FA3 for ; Tue, 19 Aug 2003 01:07:10 -0700 (PDT) (envelope-from stb@lassitu.de) Received: from [127.0.0.1] (blue.tallence.de [212.77.172.82]) (using TLSv1 with cipher EDH-RSA-DES-CBC3-SHA (168/168 bits)) (No client certificate requested) by rohrpostix.tallence.de (Postfix) with ESMTP id 537311ADA07; Tue, 19 Aug 2003 10:07:07 +0200 (CEST) Date: Tue, 19 Aug 2003 10:07:04 +0200 From: Stefan Bethke To: freebsd-current@freebsd.org Message-ID: <844382971.1061287624@[10.0.1.3]> In-Reply-To: <20030818211512.GB47959@garage.freebsd.pl> References: <2147483647.1061141322@[172.22.33.128]> <20030817224741.T320@alpha.siliconlandmark.com> <20030818030054.GA58513@dragon.nuxi.com> <20030818211512.GB47959@garage.freebsd.pl> X-Mailer: Mulberry/3.0.3 (Mac OS X) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline cc: Andre Guibert de Bruet 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 08:07:12 -0000 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 :-) Thanks all, Stefan -- Stefan Bethke, Phone +49 170 346 0140