From: Jakub Jelinek <jakub@redhat.com>
To: Andreas Schwab <schwab@suse.de>
Cc: libc-hacker@sources.redhat.com
Subject: Re: __syscall_execve on ia64
Date: Tue, 22 Oct 2002 09:04:00 -0000 [thread overview]
Message-ID: <20021022162945.A3451@sunsite.ms.mff.cuni.cz> (raw)
In-Reply-To: <jevg3vj26u.fsf@sykes.suse.de>; from schwab@suse.de on Mon, Oct 21, 2002 at 04:28:57PM +0200
On Mon, Oct 21, 2002 at 04:28:57PM +0200, Andreas Schwab wrote:
> Nobody came up with a better solution.
Well, I wrote ia64 INLINE_SYSCALL, just need to improve it a little bit
(ATM it generated warnings whenever first syscall argument was a pointer)
and submit.
But the extra for now doesn't hurt (and once INLINE_SYSCALL is in, all the
__syscall_* from ia64/syscalls.list can go away).
> 2002-10-21 Andreas Schwab <schwab@suse.de>
>
> * sysdeps/unix/sysv/linux/ia64/syscalls.list (s_execve): Set
> caller to EXTRA instead of execve, since the latter has a
> higher-priority implementation in linuxthreads.
Jakub
prev parent reply other threads:[~2002-10-22 14:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-22 7:25 Andreas Schwab
2002-10-22 9:04 ` Jakub Jelinek [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=20021022162945.A3451@sunsite.ms.mff.cuni.cz \
--to=jakub@redhat.com \
--cc=libc-hacker@sources.redhat.com \
--cc=schwab@suse.de \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).