Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 11 May 2002 15:03:30 -0700
From:      Kris Kennaway <kris@obsecurity.org>
To:        David O'Brien <obrien@FreeBSD.org>, Kris Kennaway <kris@obsecurity.org>, current@freebsd.org
Subject:   Re: embellish of bsd.cpu.mk
Message-ID:  <20020511150330.A59062@xor.obsecurity.org>
In-Reply-To: <20020511141740.A14723@dragon.nuxi.com>; from obrien@freebsd.org on Sat, May 11, 2002 at 02:17:40PM -0700
References:  <20020511133309.A14228@dragon.nuxi.com> <20020511134632.C57286@xor.obsecurity.org> <20020511141740.A14723@dragon.nuxi.com>

next in thread | previous in thread | raw e-mail | index | archive | help

--Dxnq1zWXvFF0Q93v
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Sat, May 11, 2002 at 02:17:40PM -0700, David O'Brien wrote:
> On Sat, May 11, 2002 at 01:46:32PM -0700, Kris Kennaway wrote:
> > On Sat, May 11, 2002 at 01:33:09PM -0700, David O'Brien wrote:
> >=20
> > > @@ -87,17 +113,17 @@
> > >  # presence of a CPU feature.
> > > =20
> > >  .if ${MACHINE_ARCH} =3D=3D "i386"
> > > -. if ${CPUTYPE} =3D=3D "k7"
> > > -MACHINE_CPU =3D k7 3dnow mmx k6 k5 i586 i486 i386
> > > +. if ${CPUTYPE} =3D=3D "athlon"
> > > +MACHINE_CPU =3D athlon 3dnow mmx k6 k5 i586 i486 i386
> >=20
> > This one should probably be left as k7; MACHINE_CPU is the variable
> > that is supposed to be used by applications to selectively enable
> > optimizations (so changing the name of the keyword from k7 to athlon
> > would break selection).
>=20
> Should we have "k7 athlon duron" there?

MACHINE_CPU is a list of chipset features supported by the CPU.
Unless there's any difference in the chipset features implemented by
athlon and duron (which cannot be described better by specific labels
like 3dnow or mmx), then there should just be one token to identify
them.

Having both "k7" and "athlon" would be pointless too since the
application makefile is supposed to do things like

=2Eif ${MACHINE_CPU:M3dnow}
	[enable 3dnow optimizations]
=2Eendif

and if there are two "competing" tokens to identify the athlon CPU
instruction set then there's confusion about how to test for it.

Kris



--Dxnq1zWXvFF0Q93v
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (FreeBSD)

iD8DBQE83ZUxWry0BWjoQKURAq0ZAJ9xJfvorwyQJ6jD8fmoFCC6I+Qx4wCfb9w8
0O8Ymp6m0TAh/9QUqMK1gvI=
=yPwl
-----END PGP SIGNATURE-----

--Dxnq1zWXvFF0Q93v--

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?20020511150330.A59062>