From: Marc Lehmann <pcg AT opengroup.org>
To: gcc AT gcc.gnu.org
Subject: Re: Optimization for PII
Date: Mon, 13 Sep 1999 13:00:00 -0000 [thread overview]
Message-ID: <19990913181621.A25252@cerebro.laendle> (raw)
In-Reply-To: <m11QSVf-000HVyC@rainer.informatik.uni-stuttgart.de>
On Mon, Sep 13, 1999 at 11:34:45AM +0300, Rainer Dorsch <rainer@rainer.informatik.uni-stuttgart.de> wrote:
>
> The egcs documentation says
>
> `-march=CPU TYPE'
> Generate instructions for the machine type CPU TYPE. The choices
> for CPU TYPE are: `i386', `i486', `pentium', and `pentiumpro'.
> Specifying `-march=CPU TYPE' implies `-mcpu=CPU TYPE'.
>
> It does not mention PII and PIII. Does pentiumpro run on PII and PIII or is
> there another undocumented option (I am using gcc-2.95.1)?
i386 == i486 == pentium == k6 < pentiumpro == pii == piii
(e.g. i386 code runs on pii, but pii code not on i386)
This is the view the compiler currently has. The pii and piii additional
instructions are not yet used, as isn't mmx.
It is unclear (to me) wether this will change, as there is no real strong
hierarchy anymore (chip can have mmx but not fcomi, or vice versa), or
wether additional switches (-mmx, -m3dnow) will be introduced.
--
-----==- |
----==-- _ |
---==---(_)__ __ ____ __ Marc Lehmann +--
--==---/ / _ \/ // /\ \/ / pcg@goof.com |e|
-=====/_/_//_/\_,_/ /_/\_\ XX11-RIPE --+
The choice of a GNU generation |
|
WARNING: multiple messages have this Message-ID
From: Marc Lehmann <pcg@opengroup.org>
To: gcc@gcc.gnu.org
Subject: Re: Optimization for PII
Date: Thu, 30 Sep 1999 18:02:00 -0000 [thread overview]
Message-ID: <19990913181621.A25252@cerebro.laendle> (raw)
Message-ID: <19990930180200.KJrDYiFwC63sLtbQ3t0Bv-0tAriRKycImR2mC_v9fE4@z> (raw)
In-Reply-To: <m11QSVf-000HVyC@rainer.informatik.uni-stuttgart.de>
On Mon, Sep 13, 1999 at 11:34:45AM +0300, Rainer Dorsch <rainer@rainer.informatik.uni-stuttgart.de> wrote:
>
> The egcs documentation says
>
> `-march=CPU TYPE'
> Generate instructions for the machine type CPU TYPE. The choices
> for CPU TYPE are: `i386', `i486', `pentium', and `pentiumpro'.
> Specifying `-march=CPU TYPE' implies `-mcpu=CPU TYPE'.
>
> It does not mention PII and PIII. Does pentiumpro run on PII and PIII or is
> there another undocumented option (I am using gcc-2.95.1)?
i386 == i486 == pentium == k6 < pentiumpro == pii == piii
(e.g. i386 code runs on pii, but pii code not on i386)
This is the view the compiler currently has. The pii and piii additional
instructions are not yet used, as isn't mmx.
It is unclear (to me) wether this will change, as there is no real strong
hierarchy anymore (chip can have mmx but not fcomi, or vice versa), or
wether additional switches (-mmx, -m3dnow) will be introduced.
--
-----==- |
----==-- _ |
---==---(_)__ __ ____ __ Marc Lehmann +--
--==---/ / _ \/ // /\ \/ / pcg@goof.com |e|
-=====/_/_//_/\_,_/ /_/\_\ XX11-RIPE --+
The choice of a GNU generation |
|
next prev parent reply other threads:[~1999-09-13 13:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-09-13 2:35 Rainer Dorsch
1999-09-13 13:00 ` Marc Lehmann [this message]
1999-09-30 18:02 ` Marc Lehmann
1999-09-30 18:02 ` Rainer Dorsch
1999-09-13 17:21 Mike Stump
1999-09-13 21:02 ` Richard Henderson
1999-09-13 21:34 ` Jeff Garzik
1999-09-30 18:02 ` Jeff Garzik
1999-09-30 18:02 ` Richard Henderson
1999-09-30 18:02 ` Mike Stump
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=19990913181621.A25252@cerebro.laendle \
--to=gcc@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).