From: Nicholas Wilson <nicholas.wilson@realvnc.com>
To: "musl@lists.openwall.com" <musl@lists.openwall.com>
Subject: Re: WebAssembly (Wasm) support in Musl
Date: Tue, 28 Nov 2017 13:09:14 +0000 [thread overview]
Message-ID: <VI1PR0502MB3885F5DA3D077F755B710257E73A0@VI1PR0502MB3885.eurprd05.prod.outlook.com> (raw)
In-Reply-To: <20171128130301.GL15263@port70.net>
> 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
prev parent reply other threads:[~2017-11-28 13:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-27 19:11 Nicholas Wilson
2017-11-27 20:27 ` A. Wilcox
2017-11-27 21:03 ` Jon Chesterfield
2017-11-28 13:03 ` Szabolcs Nagy
2017-11-28 13:09 ` Nicholas Wilson [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=VI1PR0502MB3885F5DA3D077F755B710257E73A0@VI1PR0502MB3885.eurprd05.prod.outlook.com \
--to=nicholas.wilson@realvnc.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).