public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Where is it written?
Date: 12 Nov 2000 21:28:29 -0800	[thread overview]
Message-ID: <8unu5t$it4$1@cesium.transmeta.com> (raw)
In-Reply-To: <20001110184031.A2704@munchkin.spectacle-pond.org> <20001111163204.B6367@inspiron.suse.de> <20001111171749.A32100@wire.cadcamlab.org> <20001112132328.C2366@athlon.random>

Followup to:  <20001112132328.C2366@athlon.random>
By author:    Andrea Arcangeli <andrea@suse.de>
In newsgroup: linux.dev.kernel
> 
> I think it doesn't worth to break binary compatilibity at this late stage.
> 
> > design such.)  One issue: ideally you want to use 64-bit regs on AMD
> > Hammer for long longs, but then you leave out all legacy x68s. :(
> 
> We can't in compatibilty mode because the rex regs are available _only_ in
> 64bit mode and even assuming the hardware would support that I would not
> recommend that since as you said that binary would not run anymore on any other
> x86 so causing pain.  Recompiling a program with native x86-64 gcc 64bit (that
> uses the 64bit ABI) is the right way to go in that case (64bit mode uses 1
> 64bit register for long long as all other 64bit architectures of course).
> 

Well, you *could* run REX32, but REX32 is not x86 (x86 code doesn't
run in REX32 mode, and REX32 code doesn't run on an x86.)

	-hpa
-- 
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
http://www.zytor.com/~hpa/puzzle.txt
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  reply	other threads:[~2000-11-13  5:29 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-10 16:37 Where is it written? George Anzinger
2000-11-10 23:40 ` Michael Meissner
2000-11-11  0:11   ` Albert D. Cahalan
2000-11-11  0:27     ` Michael Meissner
2000-11-11  1:10       ` H. Peter Anvin
2000-11-11  1:28         ` Keith Owens
2000-11-11  1:33           ` H. Peter Anvin
2000-11-14  1:33             ` Richard Henderson
2000-11-11  5:17           ` Michael Meissner
2000-11-11 14:51             ` Andrea Arcangeli
2000-11-11 15:32       ` Andrea Arcangeli
2000-11-11 23:17         ` Peter Samuelson
2000-11-11 23:30           ` H. Peter Anvin
2000-11-12  4:54             ` Peter Samuelson
2000-11-12  5:21               ` H. Peter Anvin
2000-11-12  5:36                 ` Peter Samuelson
2000-11-12  5:55                   ` Keith Owens
2000-11-12  9:35                 ` Andi Kleen
2000-11-12 12:23           ` Andrea Arcangeli
2000-11-13  5:28             ` H. Peter Anvin [this message]
2000-11-12 15:35           ` Olaf Titz
2000-11-11  1:06     ` H. Peter Anvin
2000-11-10 23:49 ` H. Peter Anvin

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='8unu5t$it4$1@cesium.transmeta.com' \
    --to=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.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