public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Randy.Dunlap" <rddunlap@osdl.org>
To: "H. J. Lu" <hjl@lucon.org>
Cc: gcc@gcc.gnu.org
Subject: Re: What to call Intel ia32e processor?
Date: Fri, 27 Feb 2004 18:10:00 -0000	[thread overview]
Message-ID: <20040227095313.774f51d2.rddunlap@osdl.org> (raw)
In-Reply-To: <20040227173413.GA12585@lucon.org>

On Fri, 27 Feb 2004 09:34:13 -0800 H. J. Lu wrote:

| We'd like to add a new target to gcc for Intel ia32e processor. But
| we couldn't find a suitable name. We don't want to use pentium4xxxx.
| The first ia32e processor has the code name Prescott. But not all
| Prescott processors support ia32e. We can use ia32e-os. But ia32e
| is an instruction set and there will be more processors implementing
| ia32e. Does anyone have any suggestions?

Should it be very processor-specific?

If not, how about ix8664 or ix64?

Or are those too confusing due to other similar names?

or ix86et?

--
~Randy

  reply	other threads:[~2004-02-27 17:53 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-27 17:50 H. J. Lu
2004-02-27 18:10 ` Randy.Dunlap [this message]
2004-02-27 18:16   ` law
2004-02-27 18:17     ` Karel Gardas
2004-02-27 18:17     ` Randy.Dunlap
2004-02-27 19:10       ` H. J. Lu
2004-02-29 22:17         ` Gerald Pfeifer
2004-03-01  0:46           ` H. J. Lu
2004-03-01  1:29             ` Daniel Jacobowitz
2004-03-01 19:00             ` Joe Buck
2004-03-01 19:47               ` H. J. Lu
2004-03-01  9:17         ` Allan Sandfeld
2004-03-01 16:53           ` H. J. Lu
2004-02-27 18:25     ` Paolo Carlini
2004-02-27 18:41       ` law
2004-02-27 18:52         ` Daniel Berlin
2004-02-27 22:41           ` Arnaud Charlet
2004-02-28 23:25           ` Mike Stump
2004-02-27 21:45         ` Guillermo Ballester Valor
2004-02-27 21:15 ` Jakub Jelinek
2004-02-27 22:49 ` Christoph Hellwig
2004-03-01  7:05 ` Alexandre Oliva

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=20040227095313.774f51d2.rddunlap@osdl.org \
    --to=rddunlap@osdl.org \
    --cc=gcc@gcc.gnu.org \
    --cc=hjl@lucon.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).