From: Paolo Giarrusso <blaisorblade@yahoo.it>
To: Jeff Dike <jdike@addtoit.com>
Cc: linux-kernel@vger.kernel.org,
user-mode-linux-devel@lists.sourceforge.net,
Adrian Bunk <bunk@stusta.de>
Subject: Re: [uml-devel] arch/um/sys-i386/setjmp.S: useless #ifdef _REGPARM's?
Date: Tue, 29 Aug 2006 10:26:41 +0200 (CEST) [thread overview]
Message-ID: <20060829082641.48020.qmail@web25222.mail.ukl.yahoo.com> (raw)
In-Reply-To: <20060828203514.GC6728@ccure.user-mode-linux.org>
Jeff Dike <jdike@addtoit.com> ha scritto:
> 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.
And which can still be enabled - I think fastcall is for this, and it
is still useful.
However more useful is to move many wrappers where this is possible
to headers (for instance the ones calling just
CHOOSE_MODE($me_tt,$me_skas) - moving them to headers is always
possible and saves a call).
> However, this is a potential problem with all regparam users, who
> all
> presumably use libc, so I'd imagine it works somehow.
For my knowledge, the only user is the non-UML Linux kernel, which
doesn't use libc :-).
And if you want to mix regparm and not regparm calls, you end up
marking it at a prototype level (i.e. with the old approach); GCC
could be smarter and allow specifying it at a per-header or per
header-folder level, but I do not think it does.
> > 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.
Fine... it is actually a good idea for some points (we currently
refrain from using certain things, such as futexes, because our
tricks could conflict with glibc tricks which we don't know - with
klibc it would be different).
We'll see.
Chiacchiera con i tuoi amici in tempo reale!
http://it.yahoo.com/mail_it/foot/*http://it.messenger.yahoo.com
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
prev parent reply other threads:[~2006-08-29 8:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-21 21:56 [uml-devel] arch/um/sys-i386/setjmp.S: useless #ifdef _REGPARM's? Adrian Bunk
2006-08-22 2:20 ` 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
2006-08-29 8:26 ` Paolo Giarrusso [this message]
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=20060829082641.48020.qmail@web25222.mail.ukl.yahoo.com \
--to=blaisorblade@yahoo.it \
--cc=bunk@stusta.de \
--cc=jdike@addtoit.com \
--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