[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <VI1PR0502MB3885F5DA3D077F755B710257E73A0@VI1PR0502MB3885.eurprd05.prod.outlook.com>
Date: Tue, 28 Nov 2017 13:09:14 +0000
From: Nicholas Wilson <nicholas.wilson@...lvnc.com>
To: "musl@...ts.openwall.com" <musl@...ts.openwall.com>
Subject: Re: WebAssembly (Wasm) support in Musl
> i thought there was already support for wasm somewhere,
> at least there were some discussions on this list some
> time ago.. with a quick search i could find
> https://github.com/WebAssembly/musl
> (and varius forks of it)
That's a good question!
(I think that particular github repo is a throwaway "experiment".)
The thing that people are actually using currently (including my company) is Emscripten's fork of Musl, which doesn't support the "wasm" target directly, but rather supports asm.js, a precursor to Wasm. Emscripten's fork plays around with Musl the internals quite a bit, and contains a lot of "FIXME" comments, so it's not really quite ready for pushing upstream to you yet.
Given that asm.js is being replaced with wasm, I thought that a fresh start would really be the way to go regarding getting wasm into upstream Musl.
My patches are similar in spirit to what Emscripten has done, but only support wasm (rather than asm.js), and do so natively rather than via the emscripten glue.
With wasm, a lot less glue should be needed, since it's now a pretty "normal" Clang compiler again.
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.
