[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <VI1PR0502MB3885B06479F77BAC57CD9213E7080@VI1PR0502MB3885.eurprd05.prod.outlook.com>
Date: Sat, 16 Dec 2017 13:21:39 +0000
From: Nicholas Wilson <nicholas.wilson@...lvnc.com>
To: "musl@...ts.openwall.com" <musl@...ts.openwall.com>
Subject: Re: [PATCH] split __libc_start_main.c into two files (Wasm)
On 15 December 2017 17:56, Rich Felker wrote:
> Adding a new interface boundary/contract for a particular arch _is_ a
> big request, one of the biggest types. It's a permanent added
> constraint that has to be considered in future modifications to the
> code. Probably the only bigger type is adding a new public (to
> application) interface boundary/contract.
Thanks for clarifying, I understand now. In our fork/branch, we will have to call *something* on Wasm, since initialisation is different to ELF and the default crt1.c doesn't really work for non-ELF archs.
For your information, what we'll do is call __init_libc directly from crt/wasm/crt1.c, since for the time being we need to do that to keep the prototype working. It would be nice if that were to become an accepted internal Musl interface, so that becomes "legal".
(I have though reverted the split into two files of __libc_start_main.c.)
Nick
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
