search for: __text_size

Sean, Thanks for doing this research and writing up that summary! The SECTION and MEMORY seem doable in lld as part of the ELF Writer. The one tricky part will be if the linker script defines symbols (e.g. __text_size), because those symbol names might be referenced by some object file atom. Thus they need an atom representation for lld's Resolver to see. So, the ELF Writer will need to make a first pass at the linker script and make "proxy" atoms for any symbols the linker script defines. Thes...

...ere should be no (major) surprises in that regard), but I decided that the existing documentation about the language itself was good enough to obviate the need to distill a reference for the entire ldscript language. > The one tricky part will be if the linker script defines symbols > (e.g. __text_size), because those symbol names might be > referenced by some object file atom. Thus they need an atom > representation for lld's Resolver to see. So, the ELF Writer will need > to make a first pass at the linker script and make "proxy" atoms for > any symbols the linker scr...

On Jan 2, 2013, at 5:51 PM, Sean Silva wrote: >> The one tricky part will be if the linker script defines symbols >> (e.g. __text_size), because those symbol names might be >> referenced by some object file atom. Thus they need an atom >> representation for lld's Resolver to see. So, the ELF Writer will need >> to make a first pass at the linker script and make "proxy" atoms for >> any symbol...

.../* (1) */ __text_start = .; /* (2) */ .text : { /* (3) */ *(.text); /* (4) */ *(.text.*); } __text_end = .; __text_size = __text_end - __text_start; /* (5) */ } (1) The fundamental command in linker scripts is `SECTIONS`, in which you define what input sections go into what output sections. (2) The symbol `.` represents the "location counter", a special symbol that indicates the "current addre...