From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23117 invoked by alias); 1 Mar 2004 01:29:34 -0000 Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org Received: (qmail 23110 invoked from network); 1 Mar 2004 01:29:33 -0000 Received: from unknown (HELO nevyn.them.org) (66.93.172.17) by sources.redhat.com with SMTP; 1 Mar 2004 01:29:33 -0000 Received: from drow by nevyn.them.org with local (Exim 4.30 #1 (Debian)) id 1AxcFM-0004Ys-MF; Sun, 29 Feb 2004 20:29:28 -0500 Date: Mon, 01 Mar 2004 01:29:00 -0000 From: Daniel Jacobowitz To: "H. J. Lu" Cc: Gerald Pfeifer , "Randy.Dunlap" , Jeffrey A Law , gcc@gcc.gnu.org Subject: Re: What to call Intel ia32e processor? Message-ID: <20040301012928.GA17069@nevyn.them.org> Mail-Followup-To: "H. J. Lu" , Gerald Pfeifer , "Randy.Dunlap" , Jeffrey A Law , gcc@gcc.gnu.org References: <20040227095313.774f51d2.rddunlap@osdl.org> <200402271810.i1RIAFUY026396@speedy.slc.redhat.com> <20040227101517.0d12635f.rddunlap@osdl.org> <20040227185212.GA13956@lucon.org> <20040301004614.GA7220@lucon.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040301004614.GA7220@lucon.org> User-Agent: Mutt/1.5.1i X-SW-Source: 2004-03/txt/msg00006.txt.bz2 On Sun, Feb 29, 2004 at 04:46:14PM -0800, H. J. Lu wrote: > On Sun, Feb 29, 2004 at 08:40:15PM +0100, Gerald Pfeifer wrote: > > On Fri, 27 Feb 2004, H. J. Lu wrote: > > > 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. > > > > That way a lot of software won't recognize that beast at _all_, neither > > as i386 nor as amd64 compatible. > > I only want it for gcc and you have to use it by hand like > > # ../configure ia32e-linux > > which will configure gcc to tune for Intel ia32e processor by default. > Nothing else will be affected. You could do this the way _EVERY OTHER TARGET_ besides x86 does it, with --with-cpu. Which works for x86, by the way. -- Daniel Jacobowitz MontaVista Software Debian GNU/Linux Developer