1 |
On Fri, Apr 01, 2005 at 01:52:18AM +0100, Ciaran McCreesh wrote: |
2 |
> |
3 |
> Abstract |
4 |
> ======== |
5 |
> |
6 |
> The x86 and x86-64 architectures currently use different ``KEYWORDS`` values. |
7 |
> This GLEP proposes a fix. |
8 |
> |
9 |
> Motivation |
10 |
> ========== |
11 |
> |
12 |
> Currently, Gentoo uses the ``x86`` keyword to indicate the architecture |
13 |
> used by IBM PCs with Intel 80x86 CPUs (and, of course, the clones). The |
14 |
> ``x86-64`` architecture, which is ``x86`` with a small number of |
15 |
> extensions for 64-bit numeric and 40 bit address support, is denoted by |
16 |
> the confusing ``amd64`` keyword. |
17 |
> |
18 |
|
19 |
Blame AMD, they're the ones who called the technology AMD64 :) |
20 |
|
21 |
> This situation is less than ideal for several reasons. |
22 |
> |
23 |
> Confusing and Inaccurate Name |
24 |
> ----------------------------- |
25 |
> |
26 |
> * Intel also produce x86-64 capable ('enabled' in PC marketing speak) |
27 |
> CPUs. It is likely that other vendors will follow suit at some point in |
28 |
> the future. |
29 |
> |
30 |
|
31 |
..which are still using AMD's AMD64 technology |
32 |
|
33 |
> * AMD also produce non-x86 (full) 64bit CPUs, which are covered by the |
34 |
> mips keyword rather than the amd64 keyword. |
35 |
> |
36 |
|
37 |
Because they're based on mips technology, not amd64 technology, and are |
38 |
never referred to in any AMD documentation as 'AMD64' |
39 |
|
40 |
At any rate, I think this should be left up to the AMD64 team and not |
41 |
forced on them via a GLEP. I don't think any architecture |
42 |
team appreciates being told what's good for it by people who haven't |
43 |
been dealing with the bugs :) |
44 |
|
45 |
-- |
46 |
Jon Portnoy |
47 |
avenj/irc.freenode.net |
48 |
-- |
49 |
gentoo-dev@g.o mailing list |