From: Rainer Dorsch <rainer@rainer.informatik.uni-stuttgart.de>
To: gcc@gcc.gnu.org
Subject: Optimization for PII
Date: Mon, 13 Sep 1999 02:35:00 -0000 [thread overview]
Message-ID: <m11QSVf-000HVyC@rainer.informatik.uni-stuttgart.de> (raw)
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)?
Thanks.
--
Rainer Dorsch
Abt. Rechnerarchitektur e-mail:rainer.dorsch@informatik.uni-stuttgart.de
Uni Stuttgart Tel.: 0711-7816-215
WARNING: multiple messages have this Message-ID
From: Rainer Dorsch <rainer@rainer.informatik.uni-stuttgart.de>
To: gcc@gcc.gnu.org
Subject: Optimization for PII
Date: Thu, 30 Sep 1999 18:02:00 -0000 [thread overview]
Message-ID: <m11QSVf-000HVyC@rainer.informatik.uni-stuttgart.de> (raw)
Message-ID: <19990930180200.DRDCCrU-u3D0AjXl1dSm1T2hdGNIdRYeVDBSCLYFie0@z> (raw)
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)?
Thanks.
--
Rainer Dorsch
Abt. Rechnerarchitektur e-mail:rainer.dorsch@informatik.uni-stuttgart.de
Uni Stuttgart Tel.: 0711-7816-215
next reply other threads:[~1999-09-13 2:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-09-13 2:35 Rainer Dorsch [this message]
1999-09-13 13:00 ` Marc Lehmann
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=m11QSVf-000HVyC@rainer.informatik.uni-stuttgart.de \
--to=rainer@rainer.informatik.uni-stuttgart.de \
--cc=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).