From: Andrea Arcangeli <andrea@suse.de>
To: Peter Samuelson <peter@cadcamlab.org>
Cc: Michael Meissner <meissner@spectacle-pond.org>,
"Albert D. Cahalan" <acahalan@cs.uml.edu>,
George Anzinger <george@mvista.com>,
"linux-kernel@vger.redhat.com" <linux-kernel@vger.kernel.org>
Subject: Re: Where is it written?
Date: Sun, 12 Nov 2000 13:23:28 +0100 [thread overview]
Message-ID: <20001112132328.C2366@athlon.random> (raw)
In-Reply-To: <20001110184031.A2704@munchkin.spectacle-pond.org> <200011110011.eAB0BbF244111@saturn.cs.uml.edu> <20001110192751.A2766@munchkin.spectacle-pond.org> <20001111163204.B6367@inspiron.suse.de> <20001111171749.A32100@wire.cadcamlab.org>
In-Reply-To: <20001111171749.A32100@wire.cadcamlab.org>; from peter@cadcamlab.org on Sat, Nov 11, 2000 at 05:17:49PM -0600
On Sat, Nov 11, 2000 at 05:17:49PM -0600, Peter Samuelson wrote:
> I'd say go for it -- set up a mailing list and flesh out a better x86
> ABI. [..]
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).
> AIUI gcc can cope OK with multiple ABIs to be chosen at runtime, am I
> right? IRIX, HP-UX and AIX all have both 32-bit and 64-bit ABIs.
Yes as in other systems, 32bit mode and 64bit mode needs different ABI and they
will coexist in the same system.
Andrea
-
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/
next prev parent reply other threads:[~2000-11-12 12:24 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 [this message]
2000-11-13 5:28 ` H. Peter Anvin
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=20001112132328.C2366@athlon.random \
--to=andrea@suse.de \
--cc=acahalan@cs.uml.edu \
--cc=george@mvista.com \
--cc=linux-kernel@vger.kernel.org \
--cc=meissner@spectacle-pond.org \
--cc=peter@cadcamlab.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.