[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <VI1PR0502MB38856793F3F8C2500517A821E7020@VI1PR0502MB3885.eurprd05.prod.outlook.com>
Date: Fri, 22 Dec 2017 18:01:35 +0000
From: Nicholas Wilson <nicholas.wilson@...lvnc.com>
To: "musl@...ts.openwall.com" <musl@...ts.openwall.com>
Subject: Re: Feature request: building musl in a portable way
On 22 December 2017 17:49, Rich Felker wrote:
> A bit of a historical note on this: in the late 80s and 90s there was
> an effort called "iBCS" to make a unified ABI for Intel-based unices.
> I believe a common syscall layer was part of it. It was abandoned
> after everybody realized that the Linux syscall ABI _was_, for all
> practical purposes, the unified ABI they wanted.
That's pretty much where WebAssembly is going too! At the moment, the WebAssembly "embedding environment" (the webpage) has to provide a JavaScript implementation of the external dependencies of the WebAssembly module.
There is a desire to eventually standardise that a bit - at the moment it's "whatever Musl wants". I think the conclusion will be "emulate Linux everywhere". I'm expecting some small tweaks though. For example, traditionally timezone information is stored in userland and not available via a syscall: rather than special-case SYS_open for "/etc/localtime", we might add a Wasm-specific syscall for doing it. (Naturally, this would all be done in Wasm via an override in a Wasm-specific directory.)
So it will be "Linux syscalls" - but probably with a few tweaks (as indeed Linux syscalls already differ very slightly between architectures).
Nick
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
