From: Alexander Revin <lyssdod@gmail.com>
To: musl@lists.openwall.com
Subject: Re: musl on a different syscall layer?
Date: Tue, 14 Aug 2018 01:12:56 +0200 [thread overview]
Message-ID: <CAM+zL-dNw10LZHrs3LFDpfV3pPHNNXTcgtMfKxi7jSmeeF4i=Q@mail.gmail.com> (raw)
> On Wed, Sep 17, 2014 at 7:02 PM, <u-wsnj@...ey.se> wrote:
>> On Wed, Sep 17, 2014 at 01:53:46PM -0400, Rich Felker wrote:
>>> The main requirement is having equivalent functionality available. On
>>> the BSD targets I've asked BSD folks about, there's supposedly no
>>> equivalent of futex except inthe Linux compat layer, which is pretty
>>> much a show-stopper unless/until it can be remedied. clone is a big
>>> unknown to me too. The other big potential problem is if the native
>>> syscall API requires a stack to communicate with the kernel (one or
>>> more BSDs require this, IIRC), since at least __unmapself needs to be
>>> able to call SYS_munmap and SYS_exit without a stack.
>>
>> Oh I see.
>>
>> This means "not much to hope for" (pity but good to know).
> I don't think NetBSD uses the stack for syscalls on any common
> architecture, maybe on some of the obscure ones, but maybe you don't
> want to support them.
>
> Adding futex support to NetBSD would be an interesting project; it is
> not in the compat layer at present either, so that is a good reason to
> add it. NetBSD is pretty friendly...
>
> Justin (justin@...bsd.org)
Hi guys, sorry for reviving a dead thread, but do you know if things
has changed ever since? I'm asking also because it would be nice to
unify efforts of porting musl to another archs - for example, openrisc
or m68k - though there're ports for both Linux and NetBSD, libc
support is kind of scattered over large codebase.
Best,
Alex
next reply other threads:[~2018-08-13 23:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-13 23:12 Alexander Revin [this message]
2018-08-15 0:45 ` Rich Felker
-- strict thread matches above, loose matches on Subject: below --
2014-09-17 14:57 u-wsnj
2014-09-17 17:53 ` Rich Felker
2014-09-17 18:02 ` u-wsnj
2014-09-18 8:59 ` Justin Cormack
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='CAM+zL-dNw10LZHrs3LFDpfV3pPHNNXTcgtMfKxi7jSmeeF4i=Q@mail.gmail.com' \
--to=lyssdod@gmail.com \
--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).