From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-return-91874-listarch-gcc=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 24566 invoked by alias); 27 Feb 2004 18:52:20 -0000
Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Archive: <http://gcc.gnu.org/ml/gcc/>
List-Post: <mailto:gcc@gcc.gnu.org>
List-Help: <http://gcc.gnu.org/ml/>
Sender: gcc-owner@gcc.gnu.org
Received: (qmail 24557 invoked from network); 27 Feb 2004 18:52:18 -0000
Received: from unknown (HELO rwcrmhc12.comcast.net) (216.148.227.85)
  by sources.redhat.com with SMTP; 27 Feb 2004 18:52:18 -0000
Received: from lucon.org ([24.6.43.109]) by comcast.net (rwcrmhc12) with ESMTP
          id <2004022718521201400o7h9je>; Fri, 27 Feb 2004 18:52:12 +0000
Received: by lucon.org (Postfix, from userid 1000)
	id 4F2EB64A9F; Fri, 27 Feb 2004 10:52:12 -0800 (PST)
Date: Fri, 27 Feb 2004 19:10:00 -0000
From: "H. J. Lu" <hjl@lucon.org>
To: "Randy.Dunlap" <rddunlap@osdl.org>
Cc: law@redhat.com, gcc@gcc.gnu.org
Subject: Re: What to call Intel ia32e processor?
Message-ID: <20040227185212.GA13956@lucon.org>
References: <20040227095313.774f51d2.rddunlap@osdl.org> <200402271810.i1RIAFUY026396@speedy.slc.redhat.com> <20040227101517.0d12635f.rddunlap@osdl.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20040227101517.0d12635f.rddunlap@osdl.org>
User-Agent: Mutt/1.4.1i
X-SW-Source: 2004-02/txt/msg01460.txt.bz2

On Fri, Feb 27, 2004 at 10:15:17AM -0800, Randy.Dunlap wrote:
> On Fri, 27 Feb 2004 11:10:15 -0700 law@redhat.com wrote:
> 
> | In message <20040227095313.774f51d2.rddunlap@osdl.org>, "Randy.Dunlap" writes:
> |  >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?
> | Or "x86-64" :-)
> 
> Sure, that works for me.  I don't know what HJ's reasons are;
> it sounds like he wants/needs a unique id ???

Currently, when you configure gcc for x86_64-linux, it will tune for
K8. I want a new target, which will tune for Intel ia32e processor by
default. I am using ia32e-linux for the time being.


H.J.