public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Fabian Groffen <grobian@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev]  Re: [RFC] New keywords for non-Gentoo Linux platforms
Date: Fri, 10 Oct 2008 09:15:16 +0200	[thread overview]
Message-ID: <20081010071516.GA12145@gentoo.org> (raw)
In-Reply-To: <20081010042123.f5c2b7f9.genone@gentoo.org>

On 10-10-2008 04:21:23 +0200, Marius Mauch wrote:
> > >> 	amd64-linux
> > >> 	x64-openbsd
> > >> 	x64-solaris
> > > 
> > > Is there a special reason why you're using "x64" instead of "amd64"
> > > in those cases? (IMO x64 is the most stupid name for the x86_64
> > > architecture)
> > 
> > AFAIK, that's not amd64/x86_64, but rather ia64, aka itanic aka
> > itanium. At least, that's how I'd interpret them since I've seen that
> > abbreviation made before, particularly since there's already amd64 in
> > context.
> 
> No, x64 is the marketing name Microsoft made up for x86_64 (aka amd64,
> ia32e and Intel 64), as "Windows for x86_64" doesn't sound that sexy,
> and was later adopted by Sun and others. 
> ia64/Itanium doesn't have any other alias names AFAIK.

We simply found that:
- amd64 is misleading
- em64t would be more to the point for some?
- x64 is what the vendors (Apple, Sun) advertise themselves
- amd64 doesn't make any sense for a Mac
- x64 is more like x86, whereas the complement of amd64 would more be
  i386 or ia32, but we wanted to avoid x86_64, x8664, so x64
- we were changing keywords anyway


-- 
Fabian Groffen
Gentoo on a different level



  reply	other threads:[~2008-10-10  7:15 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-09 18:11 [gentoo-dev] [RFC] New keywords for non-Gentoo Linux platforms Fabian Groffen
2008-10-09 22:05 ` Marius Mauch
2008-10-10  0:16   ` [gentoo-dev] " Duncan
2008-10-10  2:21     ` Marius Mauch
2008-10-10  7:15       ` Fabian Groffen [this message]
2008-10-10 12:40         ` Diego 'Flameeyes' Pettenò
2008-10-10 12:48           ` Fabian Groffen
2008-10-10 15:56             ` Marius Mauch
2008-10-10 16:13               ` Robert Bridge
2008-10-10 15:21         ` Ryan Hill
2008-10-10  8:56 ` [gentoo-dev] " Michael Haubenwallner
2008-10-10 12:56 ` Jeremy Olexa
2008-10-13  5:16   ` [gentoo-dev] " Steve Long
2008-10-13 14:27     ` Ciaran McCreesh
2008-10-13 17:59       ` Fabian Groffen
2008-10-14  7:48         ` Michael Haubenwallner
2008-10-15 10:20           ` [gentoo-dev] " Steve Long
2008-10-17 14:22 ` [gentoo-dev] " Michael Haubenwallner
2008-10-21 14:09   ` [gentoo-dev] " Tiziano Müller
2008-10-21 19:01     ` Fabian Groffen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20081010071516.GA12145@gentoo.org \
    --to=grobian@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox