This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.

--0-323383216-1098453716=:1370
Content-Type: TEXT/PLAIN; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: QUOTED-PRINTABLE

On Fri, 22 Oct 2004, Timo Sch=F6ler wrote:

> i'm not a friend of x86 ;) but sometimes something has to be done... so i=
=20
> went to the URL posted above and set a few CFLAGS in mk.conf as i did for=
=20
> amiga, sparc, sparc64, macppc, etc etc according to gcc's manual and the=
=20
> hardware i wanted NetBSD to run on.
>
> it runs seemless, stable and a-okay :) (as well as the other architecture=
s=20
> do)
>
> intel built the P2 as a kind of Pentium Pro (P6 architecture), but wanted=
 it=20
> to be more successful in the market. in the meantime, the P55C (Pentium M=
MX)=20
> was introduced, so they took a PPro Core, stripped the expensive full-spe=
ed=20
> L2 cache (as well as that phat ceramic package with two dies ;), replaced=
 by=20
> a not-so-well solution (more waitstates, half clockspeed IIRC, etc.) but=
=20
> added MMX (like the P55C had already).
>
> i wonder why gcc does diffenciate between (flags) 'pentiumpro' and=20
> 'pentium2', but does not (altho this would be logically correct, because=
=20
> there is that clear difference between P2 and PPro, with and w/o MMX) imp=
ly=20
> the -mmmx flag for pentium2 automatically...

 =09For gcc 3.3.3 (shipping with NetBSD 2.0) pentium2 implies
 =09mmx. From gnu/dist/gcc/gcc/config/i386/i386.c:
 =09      {"pentiumpro", PROCESSOR_PENTIUMPRO, 0},
 =09      {"pentium2", PROCESSOR_PENTIUMPRO, PTA_MMX},

 =09You may want to look at pkgsrc/devel/cpuflags to 'automatically'
 =09set compiler flags. It seems to indicate that pentium2 was
 =09introduced in gcc 3.1

--=20
 =09=09David/absolute       -- www.NetBSD.org: No hype required --
--0-323383216-1098453716=:1370--