From: Szabolcs Nagy <nsz@port70.net>
To: musl@lists.openwall.com
Subject: Re: [PATCH] split __libc_start_main.c into two files (Wasm)
Date: Fri, 15 Dec 2017 13:33:31 +0100 [thread overview]
Message-ID: <20171215123331.GG15263@port70.net> (raw)
In-Reply-To: <HE1PR0502MB3883753444B685A97C1F29D5E70B0@HE1PR0502MB3883.eurprd05.prod.outlook.com>
* Nicholas Wilson <nicholas.wilson@realvnc.com> [2017-12-15 11:34:10 +0000]:
>
> To clarify, it's not exit() itself that's a problem. Remember we're using statically-linked syscalls, so linking in exit() introduces a dependency on SYS_exit_group/SYS_exit, which Wasm pulls in as external dependencies in the host emulation environment. It would be nice to avoid linking in syscalls that aren't actually used, especially ones like SYS_exit that are a bit ugly to emulate.
>
why is exit ugly?
halting execution should not be complicated on whatever platform
how do you implement a_crash?
the c runtime uses that all over the place anyway so it's unlikely
that you can get away without process termination code.
next prev parent reply other threads:[~2017-12-15 12:33 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 [this message]
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
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=20171215123331.GG15263@port70.net \
--to=nsz@port70.net \
--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).