From: Nicholas Wilson <nicholas.wilson@realvnc.com>
To: "musl@lists.openwall.com" <musl@lists.openwall.com>
Subject: Re: [PATCH] split __libc_start_main.c into two files (Wasm)
Date: Tue, 19 Dec 2017 18:03:52 +0000 [thread overview]
Message-ID: <VI1PR0502MB3885CA1C811AF5DD46DBFFF7E70F0@VI1PR0502MB3885.eurprd05.prod.outlook.com> (raw)
In-Reply-To: <alpine.LNX.2.20.13.1712192051480.15692@monopod.intra.ispras.ru>
On 19 December 2017 17:54, Alexander Monakov wrote:
> It sounds to me that for practical use you'd want a Wasm module to correspond
> roughly to a shared library (with possibly multiple externally callable
> functions) that doesn't carry a 'main' function at all. Is that correct?
Yes, that's right. Maybe think of it though as a statically-linked shared library. We don't have dynamic linking yet, and when we do it's going to look very different to ELF (possibly/probably?). I want to get simple statically-linked modules working first, before adding a dynamic linker to the mix! In fact I know some people from Mozilla are working on dynamic linking, but I haven't looked into what they've done in detail.
Nick
next prev parent reply other threads:[~2017-12-19 18:03 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-07 14:51 Nicholas Wilson
2017-12-07 17:03 ` Rich Felker
2017-12-15 4:19 ` Rich Felker
2017-12-15 11:34 ` Nicholas Wilson
2017-12-15 12:33 ` Szabolcs Nagy
2017-12-15 13:04 ` Nicholas Wilson
2017-12-15 17:23 ` Rich Felker
2017-12-15 17:43 ` Nicholas Wilson
2017-12-15 17:56 ` Rich Felker
2017-12-16 13:21 ` Nicholas Wilson
2017-12-19 1:08 ` Rich Felker
2017-12-19 11:04 ` Nicholas Wilson
2017-12-19 15:27 ` Szabolcs Nagy
2017-12-19 15:56 ` Rich Felker
2017-12-19 17:46 ` Nicholas Wilson
2017-12-19 17:54 ` Alexander Monakov
2017-12-19 18:03 ` Nicholas Wilson [this message]
2017-12-19 21:03 ` Rich Felker
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=VI1PR0502MB3885CA1C811AF5DD46DBFFF7E70F0@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).