Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 23 Mar 2003 07:08:08 -0600
From:      Anti <fearow@attbi.com>
To:        David Schultz <das@FreeBSD.org>
Cc:        sgk@troutmask.apl.washington.edu, till@f111.hadiko.de, freebsd-current@FreeBSD.org
Subject:   Re: libm problem
Message-ID:  <20030323070808.0d3f63c0.fearow@attbi.com>
In-Reply-To: <20030323074114.GA80906@HAL9000.homeunix.com>
References:  <20030318173051.GA2322@f111.hadiko.de> <20030319131317.GA670@HAL9000.homeunix.com> <20030321235237.GA8097@f111.hadiko.de> <20030322111233.F4471@gamplex.bde.org> <20030322005435.GA8393@f111.hadiko.de> <20030322051443.GA13854@HAL9000.homeunix.com> <20030322182846.GA81615@troutmask.apl.washington.edu> <20030322123951.67271b29.fearow@attbi.com> <20030323074114.GA80906@HAL9000.homeunix.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 22 Mar 2003 23:41:14 -0800
David Schultz <das@FreeBSD.org> wrote:

> Thus spake Anti <fearow@attbi.com>:
> > On Sat, 22 Mar 2003 10:28:46 -0800
> > Steve Kargl <sgk@troutmask.apl.washington.edu> wrote:
> > 
> > > Pentium 4 is definitely broken on 5.x.  Perhaps, we should remove
> > > the footshooting.
> > > 
> > > --- bsd.cpu.mk.orig     Sat Mar 22 10:23:42 2003
> > > +++ bsd.cpu.mk  Sat Mar 22 10:27:11 2003
> > > @@ -62,7 +62,9 @@
> > >  .  elif ${CPUTYPE} == "k5"
> > >  _CPUCFLAGS = -march=pentium
> > >  .  elif ${CPUTYPE} == "p4"
> > > -_CPUCFLAGS = -march=pentium4
> > > +# XXX gcc 3.2.2 appears to generate bad code on FreeBSD 5.x
> > > +#_CPUCFLAGS = -march=pentium4
> > > +_CPUCFLAGS = -march=pentiumpro
> > >  .  elif ${CPUTYPE} == "p3"
> > >  _CPUCFLAGS = -march=pentium3
> > >  .  elif ${CPUTYPE} == "p2"
> > 
> > 
> > pentium3 would be better than pentiumpro on a p4 i think...
> 
> You would think so, but in my (limited) testing on a P3, this does
> not appear to be the case with gcc3 in -CURRENT.  Optimizing for a
> Ppro worked the best, IIRC.


yes but -current uses the closest cpu setting to the cputype you
choose, and in the case of pentium4 producing broken code the
obvious fallback would be pentium3... if the goal is optimal code
then use no higher than pentiumpro for any cputype as in -stable,
but that's more a policy decision than something to be changed in
a patch like this imo...



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030323070808.0d3f63c0.fearow>