From: Szabolcs Nagy <nsz@port70.net>
To: musl@lists.openwall.com
Subject: Re: syscall table discrepancies
Date: Sat, 18 Feb 2017 18:19:24 +0100 [thread overview]
Message-ID: <20170218171924.GM12395@port70.net> (raw)
In-Reply-To: <20170218043212.GQ1520@brightrain.aerifal.cx>
* Rich Felker <dalias@libc.org> [2017-02-17 23:32:12 -0500]:
> On Sat, Feb 18, 2017 at 03:41:29AM +0100, Szabolcs Nagy wrote:
> > > > or1k
> > > > -o__NR__llseek 62
> > > > +o__NR_llseek 62
>
> Indeed, I misread the direction of the diff. But perhaps we should use
> the upstream/reasonable name and have:
>
> #ifdef SYS__llseek
> #define SYS_llseek SYS__llseek
> #endif
>
> in src/internal/syscall.h, and use SYS_llseek in the source files.
> Thoughts?
makes sense, SYS_llseek will be the name on future 32bit archs
next prev parent reply other threads:[~2017-02-18 17:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-17 1:51 Rich Felker
2017-02-17 2:00 ` Rich Felker
2017-02-18 2:41 ` Szabolcs Nagy
2017-02-18 4:32 ` Rich Felker
2017-02-18 17:19 ` Szabolcs Nagy [this message]
2017-06-18 12:00 ` Szabolcs Nagy
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=20170218171924.GM12395@port70.net \
--to=nsz@port70.net \
--cc=musl@lists.openwall.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
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 NNTP newsgroup(s).