From: Richard Henderson <rth@cygnus.com>
To: Mike Stump <mrs@wrs.com>
Cc: gcc@gcc.gnu.org, rainer.dorsch@informatik.uni-stuttgart.de
Subject: Re: Optimization for PII
Date: Thu, 30 Sep 1999 18:02:00 -0000 [thread overview]
Message-ID: <19990913210204.A31604@cygnus.com> (raw)
Message-ID: <19990930180200._kxnIwsqlKah3hlZVpuw4lUmv7nF7mYVD5OKmEzAMoM@z> (raw)
In-Reply-To: <199909140020.RAA23613@kankakee.wrs.com>
On Mon, Sep 13, 1999 at 05:20:50PM -0700, Mike Stump wrote:
> I think we could add PII and PIII as essentially aliases to pentiumpro
> for users that don't know much about the CPU line.
I thought about this. It starts to make the specs file extremely ugly.
Just documenting things properly is probably good enough?
r~
next prev parent reply other threads:[~1999-09-30 18:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-09-13 17:21 Mike Stump
1999-09-13 21:02 ` Richard Henderson [this message]
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
-- strict thread matches above, loose matches on Subject: below --
1999-09-13 2:35 Rainer Dorsch
1999-09-13 13:00 ` Marc Lehmann
1999-09-30 18:02 ` Marc Lehmann
1999-09-30 18:02 ` Rainer Dorsch
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=19990913210204.A31604@cygnus.com \
--to=rth@cygnus.com \
--cc=gcc@gcc.gnu.org \
--cc=mrs@wrs.com \
--cc=rainer.dorsch@informatik.uni-stuttgart.de \
/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).