Re: Smaller binary size
[Thread Prev] | [Thread Next]
- Subject: Re: Smaller binary size
- From: Ori Bernstein <ori@xxxxxxxxxxxxxx>
- Reply-to: myrddin-dev@xxxxxxxxxxxxxx
- Date: Fri, 1 Dec 2017 10:43:32 -0800
- To: myrddin-dev@xxxxxxxxxxxxxx
- Cc: nml <arumakanil@xxxxxxxxx>
On Fri, 1 Dec 2017 18:04:03 +0800 nml <arumakanil@xxxxxxxxx> wrote: > Hi Ori, > > For the init calls topic, I am experimenting a solution inspired by the > Linux kernel module and U-Boot. > They solve the problem by collecting the address of the init symbols into a > dedicated section when linking. It's an interesting approach, although it'll take care to ensure that we don't lose a current guarantee with the way we generate things right now. At the moment, if you have: use foo const __init__ = { foo.bar() } it's guaranteed that __init__ in all dependencies is called before my __init__. -- Ori Bernstein <ori@xxxxxxxxxxxxxx>
Re: Smaller binary size | nml <arumakanil@xxxxxxxxx> |
Re: Smaller binary size | Andrew Chambers <andrewchamberss@xxxxxxxxx> |
Re: Smaller binary size | nml <arumakanil@xxxxxxxxx> |
Re: Smaller binary size | Ori Bernstein <ori@xxxxxxxxxxxxxx> |
Re: Smaller binary size | nml <arumakanil@xxxxxxxxx> |
- Prev by Date: Re: What is the expected section for type descriptors?
- Next by Date: Pointer arithmetic and iterations
- Previous by thread: Re: Smaller binary size
- Next by thread: Re: Smaller binary size
- Index(es):