[ILUG] braun's choice?

[Paul Jakma]

On Thu, 30 Jun 2005, Rick Moen wrote:

> Paul is of course completely missing my point, and ranting on 
> something irrelevant.  I did NOT allege that EM64T and AMD64 are 
> the same architecture.  Let me try explaining again, in smaller 
> words, this time:

Sigh.

> When AMD introduced the IA32 extensions used in Opteron chips, its 
> initial name for that spec _was x86_64_.

Sorry, nope:

http://www.amd.com/us-en/assets/content_type/white_papers_and_tech_docs/x86-64_wp.pdf

Wrong.

Again the x86_64 thing is due to things which consider - to be a 
seperator (eg GNU arch-system-os type names, package management 
systems) or simple conventions which prefer _ to - (eg CPP defines, - 
might have been special to cpp at some point).

> My point, which Paul seemingly did not comprehend, was that 
> "x86_64" has persisted as an umbrella term in part because it 
> doesn't include the name of either vendor.

Sigh..

Again:

x86-64: An *ABI*, worked out by AMD and various toolchain people

AMD64 and EMT64: two very similar but still different architectures 
which both support the x86-64 'userspace' ABI.

They are *ALL* valid terms, each describing a *different* thing.

> The industry seems not to agree with Paul.

sigh. I happen to work for an industry vendor who produces AMD64 
boxes and maintains a port of an OS to both EMT64 and AMD64, along 
with x86-64 userspace support.. I'm well aware of how the terminology 
is used in the industry, thank you very much.

>>>> existence hints at one of the problems with "lib64" directories: the
                                                  ^^^^^^^
>>>> a namespace collision with Itanium.
        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

> Again, Paul utterly misses my point.  Contrary to Paul's inference 
> I certainly nowhere claimed that "lib64" isn't a long-standing 
> convention from other multiarch machines -- and his digression on 
> that point was gloriously irrelevant to what I wrote.

Well then exactly what was your 'namespace collision' point about 
then?

Actually, dont bother answering that, cause to avoid getting back 
into endless and pointless arguments with you you're going back in my 
kill file.

*plonk*

regards,
-- 
Paul Jakma	paul at clubi.ie	paul at jakma.org	Key ID: 64A2FF6A
Fortune:
Authors are easy to get on with -- if you're fond of children.
 		-- Michael Joseph, "Observer"