SEO

Will the settings below work on an Intel Celeron (Mendocino) processor:
CFLAGS="-march=i686 -O3 -pipe"
CXXFLAGS="${CFLAGS}"

Whoever (nobody@devnull.none) wrote on Saturday 12 July 2003 02:56 in
alt.os.linux.gentoo:
> Will the settings below work on an Intel Celeron (Mendocino) processor:
> CFLAGS="-march=i686 -O3 -pipe"
> CXXFLAGS="${CFLAGS}"

Probably. I would use pentium2 instead of i686.
--
A Dieu,
Robert Zwerus - e-mail: arzie@dds.nl
ICQ UIN: 3943443 - MSN: robert_zwerus@hotmail.com

Whoever wrote:

> Will the settings below work on an Intel Celeron (Mendocino) processor:
> CFLAGS="-march=i686 -O3 -pipe"
> CXXFLAGS="${CFLAGS}"

Have a look at
http://www.freehackers.org/gentoo/gc...g_gcc3opt.html
Could be interesting for you.
Markus

On Sat, 12 Jul 2003, Robert Zwerus wrote:

> Whoever (nobody@devnull.none) wrote on Saturday 12 July 2003 02:56 in
> alt.os.linux.gentoo:
> > Will the settings below work on an Intel Celeron (Mendocino) processor:
> > CFLAGS="-march=i686 -O3 -pipe"
> > CXXFLAGS="${CFLAGS}"
>
> Probably. I would use pentium2 instead of i686.

Unfortunately, I built a complete install on another system (duron based),
thinking that the march=i686 setting would work on the target (the
Mendocino system)

Actually, it does seem to be running and stable now (I transferred the
disk into the target system yesterday).

Whoever (nobody@devnull.none) wrote on Sunday 13 July 2003 20:12 in
alt.os.linux.gentoo:
> Unfortunately, I built a complete install on another system (duron based),
> thinking that the march=i686 setting would work on the target (the
> Mendocino system)

I think that should also work. i686 is PPro and higher, right? So pentium2
is only one step more (P2 basically is PPro with MMX). You could rebuild
some important packages with pentium2 (like gcc, glibc, kde/gnome, mozilla
et al).
--
A Dieu,
Robert Zwerus - e-mail: arzie@dds.nl
ICQ UIN: 3943443 - MSN: robert_zwerus@hotmail.com

On Sun, 13 Jul 2003 21:51:54 +0200, Robert Zwerus wrote:

> Whoever (nobody@devnull.none) wrote on Sunday 13 July 2003 20:12 in
> alt.os.linux.gentoo:
>> Unfortunately, I built a complete install on another system (duron
>> based), thinking that the march=i686 setting would work on the target
>> (the Mendocino system)
>
> I think that should also work. i686 is PPro and higher, right? So
> pentium2 is only one step more (P2 basically is PPro with MMX). You
> could rebuild some important packages with pentium2 (like gcc, glibc,
> kde/gnome, mozilla et al).

Here's the relevant blurb from the gcc.gnu.org doc on gcc 3.2.2:

These -m options are defined for the i386 and x86-64 family of computers:
-mcpu=cpu-type
Tune to cpu-type everything applicable about the generated code,
except for the ABI and the set of available instructions. The choices
for cpu-type are i386, i486, i586, i686, pentium, pentium-mmx,
pentiumpro, pentium2, pentium3, pentium4, k6, k6-2, k6-3, athlon,
athlon-tbird, athlon-4, athlon-xp, athlon-mp, winchip-c6, winchip2 and
c3. While picking a specific cpu-type will schedule things
appropriately for that particular chip, the compiler will not generate
any code that does not run on the i386 without the -march=cpu-type
option being used. i586 is equivalent to pentium and i686 is
equivalent to pentiumpro. k6 and athlon are the AMD chips as opposed
to the Intel ones.
-march=cpu-type
Generate instructions for the machine type cpu-type. The choices for
cpu-type are the same as for -mcpu. Moreover, specifying
-march=cpu-type implies -mcpu=cpu-type.

There appear to be several steps between i686 and a P2 you can experiment
with. Have you tried running gcccpuopt script on the machine to see what
flags it says will work? It's pretty good at figuring out the march=
setting. Search for it, or there's a link on my page:

http://home.comcast.net/~jcunningham...imization.html

-Jeff