* What to call Intel ia32e processor?
@ 2004-02-27 17:50 H. J. Lu
2004-02-27 18:10 ` Randy.Dunlap
` (3 more replies)
0 siblings, 4 replies; 22+ messages in thread
From: H. J. Lu @ 2004-02-27 17:50 UTC (permalink / raw)
To: gcc
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?
H.J.
^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: What to call Intel ia32e processor?
2004-02-27 17:50 What to call Intel ia32e processor? H. J. Lu
@ 2004-02-27 18:10 ` Randy.Dunlap
2004-02-27 18:16 ` law
2004-02-27 21:15 ` Jakub Jelinek
` (2 subsequent siblings)
3 siblings, 1 reply; 22+ messages in thread
From: Randy.Dunlap @ 2004-02-27 18:10 UTC (permalink / raw)
To: H. J. Lu; +Cc: gcc
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
^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: What to call Intel ia32e processor?
2004-02-27 18:10 ` Randy.Dunlap
@ 2004-02-27 18:16 ` law
2004-02-27 18:17 ` Karel Gardas
` (2 more replies)
0 siblings, 3 replies; 22+ messages in thread
From: law @ 2004-02-27 18:16 UTC (permalink / raw)
To: Randy.Dunlap; +Cc: H. J. Lu, gcc
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" :-)
jeff
^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: What to call Intel ia32e processor?
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-27 18:25 ` Paolo Carlini
2 siblings, 1 reply; 22+ messages in thread
From: Randy.Dunlap @ 2004-02-27 18:17 UTC (permalink / raw)
To: law; +Cc: hjl, gcc
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 ???
--
~Randy
^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: What to call Intel ia32e processor?
2004-02-27 18:16 ` law
@ 2004-02-27 18:17 ` Karel Gardas
2004-02-27 18:17 ` Randy.Dunlap
2004-02-27 18:25 ` Paolo Carlini
2 siblings, 0 replies; 22+ messages in thread
From: Karel Gardas @ 2004-02-27 18:17 UTC (permalink / raw)
To: law; +Cc: Randy.Dunlap, H. J. Lu, gcc
On Fri, 27 Feb 2004 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" :-)
Or why not straight "amd64"? :-) Just to name things with the right
name...
Karel
--
Karel Gardas kgardas@objectsecurity.com
ObjectSecurity Ltd. http://www.objectsecurity.com
^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: What to call Intel ia32e processor?
2004-02-27 18:16 ` law
2004-02-27 18:17 ` Karel Gardas
2004-02-27 18:17 ` Randy.Dunlap
@ 2004-02-27 18:25 ` Paolo Carlini
2004-02-27 18:41 ` law
2 siblings, 1 reply; 22+ messages in thread
From: Paolo Carlini @ 2004-02-27 18:25 UTC (permalink / raw)
To: law; +Cc: Randy.Dunlap, H. J. Lu, gcc
law@redhat.com wrote:
>Or "x86-64" :-)
>
>
:-) Linus concurs.
However, I'm not sure to understand how you deal with the SSE3/3dnow
issue if you conflate the two architectures like this...
Paolo.
^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: What to call Intel ia32e processor?
2004-02-27 18:25 ` Paolo Carlini
@ 2004-02-27 18:41 ` law
2004-02-27 18:52 ` Daniel Berlin
2004-02-27 21:45 ` Guillermo Ballester Valor
0 siblings, 2 replies; 22+ messages in thread
From: law @ 2004-02-27 18:41 UTC (permalink / raw)
To: Paolo Carlini; +Cc: Randy.Dunlap, H. J. Lu, gcc
In message <403F89BB.2030308@suse.de>, Paolo Carlini writes:
>law@redhat.com wrote:
>
>>Or "x86-64" :-)
>>
>>
>:-) Linus concurs.
>
>However, I'm not sure to understand how you deal with the SSE3/3dnow
>issue if you conflate the two architectures like this...
Well, AMD64 would refer to the variant with 3dnow and, well, something
needs to refer to the variant with SSE3. Hmmmm.
jeff
^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: What to call Intel ia32e processor?
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
1 sibling, 2 replies; 22+ messages in thread
From: Daniel Berlin @ 2004-02-27 18:52 UTC (permalink / raw)
To: law; +Cc: Randy.Dunlap, gcc, Paolo Carlini, H. J. Lu
>>
>> However, I'm not sure to understand how you deal with the SSE3/3dnow
>> issue if you conflate the two architectures like this...
> Well, AMD64 would refer to the variant with 3dnow and, well, something
> needs to refer to the variant with SSE3. Hmmmm.
I know, we could call it IA64.
Oh.
Wait.
Hmmm. You guys really have named yourself into a corner here, haven't
you?
^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: What to call Intel ia32e processor?
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 9:17 ` Allan Sandfeld
0 siblings, 2 replies; 22+ messages in thread
From: H. J. Lu @ 2004-02-27 19:10 UTC (permalink / raw)
To: Randy.Dunlap; +Cc: law, gcc
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.
^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: What to call Intel ia32e processor?
2004-02-27 17:50 What to call Intel ia32e processor? H. J. Lu
2004-02-27 18:10 ` Randy.Dunlap
@ 2004-02-27 21:15 ` Jakub Jelinek
2004-02-27 22:49 ` Christoph Hellwig
2004-03-01 7:05 ` Alexandre Oliva
3 siblings, 0 replies; 22+ messages in thread
From: Jakub Jelinek @ 2004-02-27 21:15 UTC (permalink / raw)
To: H. J. Lu; +Cc: gcc
On Fri, Feb 27, 2004 at 09:34:13AM -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?
ia63? (Intel Architecture capable of 64 and 32 bits) ;)
Jakub
^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: What to call Intel ia32e processor?
2004-02-27 18:41 ` law
2004-02-27 18:52 ` Daniel Berlin
@ 2004-02-27 21:45 ` Guillermo Ballester Valor
1 sibling, 0 replies; 22+ messages in thread
From: Guillermo Ballester Valor @ 2004-02-27 21:45 UTC (permalink / raw)
To: gcc
Hello,
x86-64a -> for AMD64
x86-64i -> for Intel ia32e
The inquirer call it iAMD64 ;)
Guillermo.
On Friday 27 February 2004 19:35, law@redhat.com wrote:
> In message <403F89BB.2030308@suse.de>, Paolo Carlini writes:
> >law@redhat.com wrote:
> >>Or "x86-64" :-)
> >>
> >:-) Linus concurs.
> >
> >However, I'm not sure to understand how you deal with the SSE3/3dnow
> >issue if you conflate the two architectures like this...
>
> Well, AMD64 would refer to the variant with 3dnow and, well, something
> needs to refer to the variant with SSE3. Hmmmm.
>
> jeff
--
Guillermo Ballester Valor
gbv@oxixares.com
Ogijares, Granada SPAIN
Linux user #117181. See http://counter.li.org/
Public GPG KEY http://www.oxixares.com/~gbv/pubgpg.html
^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: What to call Intel ia32e processor?
2004-02-27 18:52 ` Daniel Berlin
@ 2004-02-27 22:41 ` Arnaud Charlet
2004-02-28 23:25 ` Mike Stump
1 sibling, 0 replies; 22+ messages in thread
From: Arnaud Charlet @ 2004-02-27 22:41 UTC (permalink / raw)
To: Daniel Berlin; +Cc: law, Randy.Dunlap, gcc, Paolo Carlini, H. J. Lu
> I know, we could call it IA64.
> Oh.
> Wait.
Well, what about ia32-64 ?
Or simply ia32e :-)
Arno
^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: What to call Intel ia32e processor?
2004-02-27 17:50 What to call Intel ia32e processor? H. J. Lu
2004-02-27 18:10 ` Randy.Dunlap
2004-02-27 21:15 ` Jakub Jelinek
@ 2004-02-27 22:49 ` Christoph Hellwig
2004-03-01 7:05 ` Alexandre Oliva
3 siblings, 0 replies; 22+ messages in thread
From: Christoph Hellwig @ 2004-02-27 22:49 UTC (permalink / raw)
To: H. J. Lu; +Cc: gcc
On Fri, Feb 27, 2004 at 09:34:13AM -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?
Wait for your marketing folks to find a name...
^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: What to call Intel ia32e processor?
2004-02-27 18:52 ` Daniel Berlin
2004-02-27 22:41 ` Arnaud Charlet
@ 2004-02-28 23:25 ` Mike Stump
1 sibling, 0 replies; 22+ messages in thread
From: Mike Stump @ 2004-02-28 23:25 UTC (permalink / raw)
To: Daniel Berlin; +Cc: law, Randy.Dunlap, gcc, Paolo Carlini, H. J. Lu
On Friday, February 27, 2004, at 10:41 AM, Daniel Berlin wrote:
> I know, we could call it IA64.
> Oh.
> Wait.
You know, we could.
^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: What to call Intel ia32e processor?
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 9:17 ` Allan Sandfeld
1 sibling, 1 reply; 22+ messages in thread
From: Gerald Pfeifer @ 2004-02-29 22:17 UTC (permalink / raw)
To: H. J. Lu; +Cc: Randy.Dunlap, Jeffrey A Law, gcc
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.
Gerald
--
Gerald Pfeifer (Jerry) gerald@pfeifer.com http://www.pfeifer.com/gerald/
^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: What to call Intel ia32e processor?
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
0 siblings, 2 replies; 22+ messages in thread
From: H. J. Lu @ 2004-03-01 0:46 UTC (permalink / raw)
To: Gerald Pfeifer; +Cc: Randy.Dunlap, Jeffrey A Law, gcc
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.
H.J.
^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: What to call Intel ia32e processor?
2004-03-01 0:46 ` H. J. Lu
@ 2004-03-01 1:29 ` Daniel Jacobowitz
2004-03-01 19:00 ` Joe Buck
1 sibling, 0 replies; 22+ messages in thread
From: Daniel Jacobowitz @ 2004-03-01 1:29 UTC (permalink / raw)
To: H. J. Lu; +Cc: Gerald Pfeifer, Randy.Dunlap, Jeffrey A Law, gcc
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
^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: What to call Intel ia32e processor?
2004-02-27 17:50 What to call Intel ia32e processor? H. J. Lu
` (2 preceding siblings ...)
2004-02-27 22:49 ` Christoph Hellwig
@ 2004-03-01 7:05 ` Alexandre Oliva
3 siblings, 0 replies; 22+ messages in thread
From: Alexandre Oliva @ 2004-03-01 7:05 UTC (permalink / raw)
To: H. J. Lu; +Cc: gcc
On Feb 27, 2004, "H. J. Lu" <hjl@lucon.org> wrote:
> We'd like to add a new target to gcc for Intel ia32e processor. But
> we couldn't find a suitable name.
Wouldn't AMD64i be appropriate? :-P :-)
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Happy GNU Year! oliva@{lsd.ic.unicamp.br, gnu.org}
Red Hat GCC Developer aoliva@{redhat.com, gcc.gnu.org}
Free Software Evangelist Professional serial bug killer
^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: What to call Intel ia32e processor?
2004-02-27 19:10 ` H. J. Lu
2004-02-29 22:17 ` Gerald Pfeifer
@ 2004-03-01 9:17 ` Allan Sandfeld
2004-03-01 16:53 ` H. J. Lu
1 sibling, 1 reply; 22+ messages in thread
From: Allan Sandfeld @ 2004-03-01 9:17 UTC (permalink / raw)
To: gcc
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.
^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: What to call Intel ia32e processor?
2004-03-01 9:17 ` Allan Sandfeld
@ 2004-03-01 16:53 ` H. J. Lu
0 siblings, 0 replies; 22+ messages in thread
From: H. J. Lu @ 2004-03-01 16:53 UTC (permalink / raw)
To: Allan Sandfeld; +Cc: gcc
On Mon, Mar 01, 2004 at 10:20:21AM +0100, Allan Sandfeld 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.
> >
> What is the problem with that?
>
> Athlons are recognized as i686 and turned like a Pentium pro. If you want
That is not true.
> specific optimizations you should use mcpu.
H.J.
^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: What to call Intel ia32e processor?
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
1 sibling, 1 reply; 22+ messages in thread
From: Joe Buck @ 2004-03-01 19:00 UTC (permalink / raw)
To: H. J. Lu; +Cc: Gerald Pfeifer, Randy.Dunlap, Jeffrey A Law, gcc
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.
Please don't inflict that on any external users. As others have said,
the way we handle the different flavors of one processor family is with
--with-cpu.
^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: What to call Intel ia32e processor?
2004-03-01 19:00 ` Joe Buck
@ 2004-03-01 19:47 ` H. J. Lu
0 siblings, 0 replies; 22+ messages in thread
From: H. J. Lu @ 2004-03-01 19:47 UTC (permalink / raw)
To: Joe Buck; +Cc: Gerald Pfeifer, Randy.Dunlap, Jeffrey A Law, gcc
On Mon, Mar 01, 2004 at 11:00:39AM -0800, Joe Buck wrote:
> 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.
>
> Please don't inflict that on any external users. As others have said,
> the way we handle the different flavors of one processor family is with
> --with-cpu.
Gcc can be configured with k8-linux, opteron-linux and athlon_64-linux.
I'd like to have something silimar to that.
H.J.
^ permalink raw reply [flat|nested] 22+ messages in thread
end of thread, other threads:[~2004-03-01 19:47 UTC | newest]
Thread overview: 22+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2004-02-27 17:50 What to call Intel ia32e processor? H. J. Lu
2004-02-27 18:10 ` Randy.Dunlap
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
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).