mp is the multi-processor version. If you have a multi-processor machine,
you have dual mp procs, and should use that setting. xp is for single-cpu
systems, and can't be dualed up (without hacking - I think I remember
something on Tom's Hardware that used pencil lead to short out two xp leads
to force dual capability). I've tried running an xp proc on an mp
(multi-proc) motherboard and it didn't work. Had to switch to an mp proc
(more expensive).

So, in sum, for an mp dual machine, use -march=athlon-mp (note that -march
implies -mcpu, so if you use -march you do not need to specify -mcpu as it's
already set by default).

Eric

> -----Original Message-----
> From: brett holcomb [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, March 04, 2003 4:04 PM
> To: [EMAIL PROTECTED]
> Subject: Re: [gentoo-user] chost, cflags, and cxxflags examples
>
>
> It depends on the Athlon.  AMD has XP and MP versions of
> the cpus.  Richard may have the XP version.  Since I have
> the MP version I used it.
>
> On Tue, 04 Mar 2003 16:04:08 -0500
>   Jason Giangrande <[EMAIL PROTECTED]> wrote:
> >Thanks.  Quick question, though.  Why athlon-xp instead
> >of athlon-mp?
> >
> >Jason
> >
> >Richard Kilgore wrote:
> >
> >>On Tue, Mar 04, 2003 at 03:44:32PM -0500, Jason
> >>Giangrande wrote:
> >>
> >>
> >>>Anyone have any examples of the CFLAGS and CXXFLAGS
> >>>settings  for a dual Athlon system or know of any links
> >>>that explain these settings more?
> >>>
> >>>Thanks.
> >>>
> >>>
> >>
> >>Here is what I use.  I think I just used the comments in
> >>make.conf.
> >>
> >>   CHOST="i686-pc-linux-gnu"
> >>   CFLAGS="-march=athlon-xp -mcpu=athlon-xp -O3 -pipe"
> >>   CXXFLAGS="${CFLAGS}"
> >>   MAKEOPTS="-j3"
> >>
> >>   - richard
> >>
> >>
> >>
> >
> >--
> >-Jason Giangrande
> >  giangrande.org - http://www.giangrande.org
> ><http://www.giangrande.org/>
> >  Dog's I View - http://www.dogsiview.com
> ><http://www.dogsiview.com/>
> >
> >
> >--
> >[EMAIL PROTECTED] mailing list
> >
>
>
> --
> [EMAIL PROTECTED] mailing list
>
>


--
[EMAIL PROTECTED] mailing list

Reply via email to