This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: What to call Intel ia32e processor?
- From: Allan Sandfeld <linux at sneulv dot dk>
- To: gcc at gcc dot gnu dot org
- Date: Mon, 1 Mar 2004 10:20:21 +0100
- Subject: Re: What to call Intel ia32e processor?
- References: <20040227095313.774f51d2.rddunlap@osdl.org> <20040227101517.0d12635f.rddunlap@osdl.org> <20040227185212.GA13956@lucon.org>
On Friday 27 February 2004 19:52, H. J. Lu wrote:
> 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.
>
What is the problem with that?
Athlons are recognized as i686 and turned like a Pentium pro. If you want
specific optimizations you should use mcpu.