From: "H. J. Lu" <hjl@lucon.org>
To: linux-ia64@vger.kernel.org
Subject: Re: Inefficient ia64 system call implementation in glibc
Date: Mon, 22 Sep 2003 19:39:18 +0000 [thread overview]
Message-ID: <marc-linux-ia64-106425957923121@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-106398916511816@msgid-missing>
On Sun, Sep 21, 2003 at 02:04:34PM -0700, Richard Henderson wrote:
> On Fri, Sep 19, 2003 at 09:32:18AM -0700, H. J. Lu wrote:
> > The basically problem is glibc doesn't store information about what
> > the kernel interface is so that it can't efficiently set up parameters
> > for system calls. Is there a way to improve the situation?
>
> Use __typeof instead of hard-coding long in the LOAD_ARGS macros.
> That's where the extension comes from.
How can I make __typeof to work with
char buf [300];
INLINE_SYSCALL (read, 3, fd, buf, sizeof buf);
Can I get char * from char [300]?
H.J.
next prev parent reply other threads:[~2003-09-22 19:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-19 16:32 Inefficient ia64 system call implementation in glibc H. J. Lu
2003-09-19 17:29 ` Grant Grundler
2003-09-19 21:46 ` John Worley
2003-09-19 23:32 ` Jim Hull
2003-09-20 13:01 ` Andreas Schwab
2003-09-21 21:04 ` Richard Henderson
2003-09-22 19:39 ` H. J. Lu [this message]
2003-09-22 21:25 ` David Mosberger
2003-09-22 23:21 ` Richard Henderson
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-106425957923121@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