From: Dan Armak <ermak@netvision.net.il>
To: gentoo-dev@cvs.gentoo.org
Subject: Re: [gentoo-dev] make.conf optimization flags for k6, athlon
Date: Sun Jul 15 00:15:02 2001 [thread overview]
Message-ID: <01071509140900.00688@localhost> (raw)
In-Reply-To: <20010715.543000@localhost.localdomain>
On Sunday 15 July 2001 03:54, you wrote:
> A few comments I've been meaning to make.
>
> 1. According to the GCC documentation you shouldn't be using -m<processor>
> any more. It's been depreciated in favor of -mcpu<processor>.
I know that. The mpentium etc. flags wre in the originl make.conf, the things
I added were -march=x -mcpu=x. I'll change mpentium for march=pentium if I
haven't already.
>
> 2. You don't need to use -mcpu usually with -march as -march sets -mcpu
> for you. I say usually 'cause there's an AMD processor (can't remember
> which) that uses a different instruction set than the default set by the
> -march it uses.
I think you're wrong. If I say march=i486 mcpu=i586 this means the binary
will run on any 486 or better, but is optimized for the 586.
>
> 3. The usage of processor names has been depreciated as well. Should
> use i586, etc. instead.
For intel processors maybe. However AMD's k6, though a 586, is better than a
Pentium, and the Athlon, though a 686, is better than a Pentium3.
Although it really would be better if gcc allowed for flags of instruction
sets etc. so that you could define your 'custom processor' by saying, use
MMX+3DNow!2+sse. Than we'd know exactly what optimization it was doing.
Dan Armak
next prev parent reply other threads:[~2001-07-15 6:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-13 14:36 [gentoo-dev] make.conf optimization flags for k6, athlon Dan Armak
2001-07-13 14:55 ` Daniel Robbins
2001-07-13 15:00 ` Dan Armak
2001-07-13 15:38 ` Daniel Robbins
2001-07-14 1:11 ` Dan Armak
2001-07-14 2:12 ` Daniel Robbins
2001-07-14 3:28 ` Hendrik Visage
2001-07-14 4:04 ` Dan Armak
2001-07-14 18:56 ` Thomas Beaudry
2001-07-15 0:15 ` Dan Armak [this message]
2001-07-15 0:45 ` Thomas Beaudry
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=01071509140900.00688@localhost \
--to=ermak@netvision.net.il \
--cc=gentoo-dev@cvs.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox