mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Rich Felker <dalias@libc.org>
To: musl@lists.openwall.com
Subject: Re: [PATCH] split __libc_start_main.c into two files (Wasm)
Date: Thu, 7 Dec 2017 12:03:56 -0500	[thread overview]
Message-ID: <20171207170356.GX1627@brightrain.aerifal.cx> (raw)
In-Reply-To: <VI1PR0502MB3885AB4C92D5B2A5515436F0E7330@VI1PR0502MB3885.eurprd05.prod.outlook.com>

On Thu, Dec 07, 2017 at 02:51:31PM +0000, Nicholas Wilson wrote:
> Hi,
> 
> I've got some more patches to try and get in for Wasm support.
> 
> Here's one that should be fairly straightforward? In Musl, most
> (non-static) functions are in a file of their own, which is good
> from a linkage point of view.
> 
> I'd like to have __libc_start_main.c split into two files, because
> for Wasm I'd like to be able to call __libc_start_init (from within
> the CRT directory) but without having to link in exit(), since many
> Wasm applications will never call exit() and won't necessarily use
> main.
> 
> There's no pollution of the codebase, it's purely splitting a file.
> 
> Patch below.

__libc_start_init is intentionally not a public interface but part of
musl internals. There is no reason to assume it will continue to exist
with the same name or interface in future versions of musl. The public
interface for the entry point is __libc_start_main.

exit() is literally 9 instructions on x86_64, and likely comparably
small elsewhere. I don't see how trying to optimize it out makes
sense. The bulk of the code that runs at exit() when there's
nontrivial work to do at exit time is linked through dependencies from
other sources like stdio and atexit, and would be linked even if you
succeeded in optimizing exit out.

Rich


  reply	other threads:[~2017-12-07 17: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 [this message]
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
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=20171207170356.GX1627@brightrain.aerifal.cx \
    --to=dalias@libc.org \
    --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).