From: "H. J. Lu" <hjl@lucon.org>
To: linux-ia64@vger.kernel.org
Subject: Re: PATCH: Re: Inefficient ia64 system call implementation in glibc
Date: Thu, 25 Sep 2003 04:39:29 +0000 [thread overview]
Message-ID: <marc-linux-ia64-106446478203532@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-106438485815490@msgid-missing>
On Wed, Sep 24, 2003 at 09:43:19AM +0200, Jakub Jelinek wrote:
> On Wed, Sep 24, 2003 at 10:36:21AM +0200, Andreas Schwab wrote:
> > >> x+0 would work in this case; I'd guess it'd work for most of the
> > >> cases that syscalls need to handle.
> > >>
> > >
> > > This patch works for me.
> > >
> > >
> > > H.J.
> > > ---
> > > 2003-09-22 H.J. Lu <hongjiu.lu@intel.com>
> > >
> > > * sysdeps/unix/sysv/linux/ia64/sysdep.h (LOAD_ARGS_1): Use
> > > __typeof ((outX) + 0) instead of long.
> >
> > Hopefully we don't have any occurences of LOAD_ARGS_n(...,0,..) where the
> > kernel expects long.
>
> I think that's very risky and could mean hard to find bugs.
> I don't think the 0-1 cycle speedup is not worth the troubles.
I don't think it is any riskier than using long. Those are internal
to libc. We don't have to worry about any users will misuse them. We
just have to make sure we pass the right types of arguments to kernel
in glibc. I don't think it is too much to ask.
H.J.
prev parent reply other threads:[~2003-09-25 4:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-24 6:27 PATCH: Re: Inefficient ia64 system call implementation in glibc H. J. Lu
2003-09-24 7:43 ` Jakub Jelinek
2003-09-24 8:36 ` Andreas Schwab
2003-09-24 18:56 ` H. J. Lu
2003-09-24 20:36 ` Andreas Schwab
2003-09-24 21:12 ` Jim Wilson
2003-09-25 4:34 ` H. J. Lu
2003-09-25 4:36 ` H. J. Lu
2003-09-25 4:39 ` H. J. Lu [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=marc-linux-ia64-106446478203532@msgid-missing \
--to=hjl@lucon.org \
--cc=linux-ia64@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