On Sun, Mar 23, 2003 at 07:08:08AM -0600, Anti wrote:
> On Sat, 22 Mar 2003 23:41:14 -0800
> David Schultz <[EMAIL PROTECTED]> wrote:
>
> > Thus spake Anti <[EMAIL PROTECTED]>:
> > > On Sat, 22 Mar 2003 10:28:46 -0800
> > > Steve Kargl <[EMAIL PROTECTED]> 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
why not
+_CPUCFLAGS = -march=pentium4 -mno-sse2
> choose, and in the case of pentium4 producing broken code the
> obvious fallback would be pentium3...
above would be in fact the same because only the SSE2 code differs from
march=pentium3 which in turn only defines SSE additionally (which
probably generates the slower code compared to pentiumpro) as i see it.
code generation for all x86 uses the same rules (i386.md)
except that some rules only apply if TARGET_SSE2 is defined.
till
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
