public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Dike <jdike@addtoit.com>
To: Blaisorblade <blaisorblade@yahoo.it>
Cc: user-mode-linux-devel@lists.sourceforge.net,
	Adrian Bunk <bunk@stusta.de>,
	linux-kernel@vger.kernel.org
Subject: Re: [uml-devel] arch/um/sys-i386/setjmp.S: useless #ifdef _REGPARM's?
Date: Mon, 28 Aug 2006 16:35:14 -0400	[thread overview]
Message-ID: <20060828203514.GC6728@ccure.user-mode-linux.org> (raw)
In-Reply-To: <200608261256.36654.blaisorblade@yahoo.it>

On Sat, Aug 26, 2006 at 12:56:36PM +0200, Blaisorblade wrote:
> Can anybody explain me how can we use REGPARM if we have to link with host 
> glibc?

Umm, yeah, good point.  This regparam behavior is different from the old
behavior, where regparam functions had to be declared as such.

However, this is a potential problem with all regparam users, who all
presumably use libc, so I'd imagine it works somehow.

> If we are going to use klibc instead of glibc that's ok (and this is not the 
> case I'm talking about), but I do not know that plan (and nobody discussed 
> the implications).

I've been idly considering that, but it's no more than idle consideration
right now.

				Jeff

  reply	other threads:[~2006-08-28 20:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-21 21:56 arch/um/sys-i386/setjmp.S: useless #ifdef _REGPARM's? Adrian Bunk
2006-08-22  2:20 ` [uml-devel] " Jeff Dike
2006-08-22 16:07   ` Adrian Bunk
2006-08-22 17:42     ` Jeff Dike
2006-08-22 19:28       ` Adrian Bunk
2006-08-26 10:56 ` Blaisorblade
2006-08-28 20:35   ` Jeff Dike [this message]
2006-08-29  8:26     ` Paolo Giarrusso

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=20060828203514.GC6728@ccure.user-mode-linux.org \
    --to=jdike@addtoit.com \
    --cc=blaisorblade@yahoo.it \
    --cc=bunk@stusta.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=user-mode-linux-devel@lists.sourceforge.net \
    /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