AMD64 and lang/gcc3x on -CURRENT

[James Van Artsdalen]

> From: Peter Wemm <peter at wemm.org>
> Date: Sun, 22 Feb 2004 00:57:36 -0800
> 
> On Wednesday 18 February 2004 12:37 am, Gerald Pfeifer wrote:
> > > 1) AMD didn't give the platform an official name till fairly late
> > > 2) Some folks chose amd64
> > > 3) Later the muttonheads at the FSF chose x86_64
> >
> > And right they were.  See yesterdays press announcement by Intel.
> 
> That sequence of events isn't quite right.  AMD originally came up with 
> x86-64.  When Microsoft got going on the port, they said "that name 
> sucks to type, how about amd64?  We're NOT using x86=64".  And so it 
> became "amd64" or AMD64.  And FWIW, I agree.  x86_64 is the worst 
> possible name to type.

My understanding is that the linux crowd picked x86_64 and Microsoft
and FreeBSD picked amd64.  At this point everyone, except Microsoft,
has done releases and systems are deployed and in the field.  It's too
late to go back and make changes without good reason: configure scripts
need to accept both.

Why not something like to solve the heartburn?  There's still a
collision of some sort between freebsd.h and x86_64.h that needs to be
solved, but that's a different issue.

*** config.guess.~1~	Thu Jan 30 17:25:36 2003
--- config.guess	Sun Feb 22 20:41:42 2004
***************
*** 759,764 ****
--- 759,767 ----
  	#endif
  EOF
  	eval `$CC_FOR_BUILD -E $dummy.c 2>/dev/null | grep ^LIBC=`
+ 	if [ ".$UNAME_MACHINE" = ".amd64" ] ; then
+ 	    UNAME_MACHINE=x86_64
+ 	fi
  	echo ${UNAME_MACHINE}-unknown-freebsd`echo ${UNAME_RELEASE}|sed -e 's/[-(].*//'`${LIBC:+-$LIBC}
  	exit 0 ;;
      i*:CYGWIN*:*)