public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@transmeta.com>
To: Peter Samuelson <peter@cadcamlab.org>
Cc: "H. Peter Anvin" <hpa@zytor.com>, linux-kernel@vger.kernel.org
Subject: Re: Where is it written?
Date: Sat, 11 Nov 2000 21:21:01 -0800	[thread overview]
Message-ID: <3A0E28BD.CCA5D85F@transmeta.com> (raw)
In-Reply-To: <20001110184031.A2704@munchkin.spectacle-pond.org> <20001110192751.A2766@munchkin.spectacle-pond.org> <20001111163204.B6367@inspiron.suse.de> <20001111171749.A32100@wire.cadcamlab.org> <8ukkr3$f2h$1@cesium.transmeta.com> <20001111225428.A20749@wire.cadcamlab.org>

Peter Samuelson wrote:
> 
> [Peter Anvin]
> > At the time the original x86 ABI was created, a lot of C code was
> > still K&R, and thus prototypes didn't exist...
> 
> True enough.  That does explain a lot.  But what about the Alpha?  From
> reading gcc source awhile back I seem to remember that most if not all
> parameters are passed in registers.  How does *that* work with varargs
> and no prototypes?  Or does it?
> 

It doesn't, but the Alpha is a *much* more recent ABI... the x86 ABI
really dates back to the 16-bit 8086-series CPUs.

> > I don't think we want to introduce a new ABI in user space at this
> > time.  If we ever have to major-rev the ABI (libc.so.7), then we
> > should consider this.
> 
> Ah, but kernel-side?  My point was that if gcc (and binutils) is
> flexible enough to let you pick an ABI at runtime, perhaps a RISCoid
> ABI for x86 could coexist with the SysV one, to be used initially for
> self-contained code like the kernel.  (And later, a possible transition
> in userspace.)

We tried once; at that point the register-based ABI support in gcc was
too buggy to be useful.  We might try again in 2.5 since we now have
increased the minimum gcc version for kernel compiles.  Binutils needs no
change.

	-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-12  5:21 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 [this message]
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
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=3A0E28BD.CCA5D85F@transmeta.com \
    --to=hpa@transmeta.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox