From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Where is it written?
Date: 11 Nov 2000 15:30:43 -0800 [thread overview]
Message-ID: <8ukkr3$f2h$1@cesium.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>
Followup to: <20001111171749.A32100@wire.cadcamlab.org>
By author: Peter Samuelson <peter@cadcamlab.org>
In newsgroup: linux.dev.kernel
>
> [Andrea Arcangeli]
> > Can you think at one case where it's better to push the parameter on
> > the stack instead of passing them through the callee clobbered
> > ebx/eax/edx?
>
> Well it's safer if you are lazy about prototyping varargs functions.
> But of course by doing that you're treading on thin ice anyway, in
> terms of type promotion and portability. So I guess it's much better
> to say "varargs functions MUST be prototyped" and use the registers.
>
It definitely is now. At the time the original x86 ABI was created, a
lot of C code was still K&R, and thus prototypes didn't exist...
>
> 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.
>
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.
-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/
next prev parent reply other threads:[~2000-11-11 23:31 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 [this message]
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
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='8ukkr3$f2h$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 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.