mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Nicholas Wilson <nicholas.wilson@realvnc.com>
To: "musl@lists.openwall.com" <musl@lists.openwall.com>
Subject: WebAssembly (Wasm) support in Musl
Date: Mon, 27 Nov 2017 19:11:44 +0000	[thread overview]
Message-ID: <VI1PR0502MB38851750FE8A6618D00EA875E7250@VI1PR0502MB3885.eurprd05.prod.outlook.com> (raw)

Hi,

I'm interested in the plans for WebAssembly support in Musl.

(Background: WebAssembly is a new portable Virtual Machine instruction set, designed for use in browsers to run performance-critical code. It's supported now in all major browsers, and could be a significant part of the web platform in future.)

The Emscripten project has previously used Musl internally, based on a fork, and that's using a quite complicated compiler that performs many legacy pre- and post-processing stages. (I have previously contributed to LLVM and Emscripten, but I'm not affiliated with either project.)

Recently, LLVM/Clang have been working on a brand new & clean compiler target, designed to generate WebAssembly output directly in a clean way, without Emscripten's existing convoluted intermediate steps. The native Clang support for WebAssembly is nearing the point where it's ready to use - at which point it will need a libc!

I'd like to see that added to Musl natively, as part of the upstream release. Is that something that you would be willing to accept patches for?

I've got some patches ready, and apart from adding some new directories ("arch/wasm", "src/internal/wasm") there are hardly any changes at all needed to the core code to get it all compiling for Wasm.

All the best,
Nick

---
Nick Wilson
RealVNC Ltd

             reply	other threads:[~2017-11-27 19:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-27 19:11 Nicholas Wilson [this message]
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

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=VI1PR0502MB38851750FE8A6618D00EA875E7250@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).