mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Michael Meissner <meissner@spectacle-pond.org>
To: Keith Owens <kaos@ocs.com.au>
Cc: "H. Peter Anvin" <hpa@zytor.com>, linux-kernel@vger.kernel.org
Subject: Re: Where is it written?
Date: Sat, 11 Nov 2000 00:17:04 -0500	[thread overview]
Message-ID: <20001111001704.B2766@munchkin.spectacle-pond.org> (raw)
In-Reply-To: <8ui698$c2q$1@cesium.transmeta.com> <11198.973906134@ocs3.ocs-net>
In-Reply-To: <11198.973906134@ocs3.ocs-net>; from kaos@ocs.com.au on Sat, Nov 11, 2000 at 12:28:54PM +1100

On Sat, Nov 11, 2000 at 12:28:54PM +1100, Keith Owens wrote:
> On 10 Nov 2000 17:10:00 -0800, 
> "H. Peter Anvin" <hpa@zytor.com> wrote:
> >We can mess with the ABI, but it requires a wholescale rev of the
> >entire system.
> 
> AFAICT, there is nothing stopping us from redoing the kernel ABI to
> pass the first few parameters between kernel functions in registers.
> As long as the syscall interface is unchanged, that ABI change will
> only break binary modules (care_factor == 0).  The ABI type would need
> to be added to the symbol version prefix, trivial.

Other than the minor little fact that -mregparm=n exposes several latent
compiler bugs, that since it is not part of the ABI, it isn't on anybody's
radar screen as needing to be fixed.  This is of course the downside of free
software, that volunteers tend to have their own ideas of what to work on.

Also note, that for -mregpar=n, it is important that variable argument
functions be declared properly in all callers, since they need to use the
standard calling sequence.

-- 
Michael Meissner, Red Hat, Inc.
PMB 198, 174 Littleton Road #3, Westford, Massachusetts 01886, USA
Work:	  meissner@redhat.com		phone: +1 978-486-9304
Non-work: meissner@spectacle-pond.org	fax:   +1 978-692-4482
-
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/

  parent reply	other threads:[~2000-11-11  5:17 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-10 16:37 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 [this message]
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
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=20001111001704.B2766@munchkin.spectacle-pond.org \
    --to=meissner@spectacle-pond.org \
    --cc=hpa@zytor.com \
    --cc=kaos@ocs.com.au \
    --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

all inboxes | Powered by JetHome®