Date: Tue, 19 Aug 2003 10:07:04 +0200 From: Stefan Bethke <stb@lassitu.de> To: freebsd-current@freebsd.org Cc: Andre Guibert de Bruet <andy@siliconlandmark.com> Subject: Re: CPUTYPE considered harmful? (was: Lot's of SIGILL, SIGSEGV) 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>
next in thread | previous in thread | raw e-mail | index | archive | help
On Montag, 18. August 2003 23:15 Uhr +0200 Pawel Jakub Dawidek <nick@garage.freebsd.pl> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?844382971.1061287624>