From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Algorithm for CPU_X86
Date: 3 Jun 2002 22:19:12 -0700 [thread overview]
Message-ID: <adhikg$tcc$1@cesium.transmeta.com> (raw)
In-Reply-To: <20020604031840.GA4289@werewolf.able.es>
Followup to: <20020604031840.GA4289@werewolf.able.es>
By author: "J.A. Magallon" <jamagallon@able.es>
In newsgroup: linux.dev.kernel
>
> Following with the cpu selection changes, setting the flags controlled
> by the various CPU_X86_xxxx can be a real mess.
>
> But, I have ralized that those CPU_X86 flags can be logically split in
> two groups: features (TSC,MMX,3DNOW) and bugfixes (PPRO_FENCE) (or perhaps
> more, it is just a first thought...).
>
Don't forget optimizations. It's a big difference between "optimize
for" and "require" -- consider gcc, which have -mcpu= and -march=
respectively for the two.
-hpa
--
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
http://www.zytor.com/~hpa/puzzle.txt <amsp@zytor.com>
prev parent reply other threads:[~2002-06-04 5:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-04 3:18 Algorithm for CPU_X86 J.A. Magallon
2002-06-04 4:28 ` Ghozlane Toumi
2002-06-04 5:19 ` H. Peter Anvin [this message]
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='adhikg$tcc$1@cesium.transmeta.com' \
--to=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.