Displaying 2 results from an estimated 2 matches for "linker_input_section".
2018 May 11
2
[RFC] (Thin)LTO with Linker Scripts
...to LTO. They should therefore not be the default behavior,
but be
guarded under a clang flag, e.g. "-flto-ls", which is passed in addition to
-flto[=thin], when the user knows that their linker has this capability.
Note: In the presentation, we proposed a dedicated attribute
"linker_input_section" instead of using the explicit section attribute.
After discussions with Peter, I believe we don't need to introduce an
additional attribute.
Step 2: Symbol resolution in the linker
=======================================
The linker loads all bitcode input files and performs symbol...
2018 May 14
0
[RFC] (Thin)LTO with Linker Scripts
...ore not be the default behavior, but
> be
> guarded under a clang flag, e.g. "-flto-ls", which is passed in addition to
> -flto[=thin], when the user knows that their linker has this capability.
>
> Note: In the presentation, we proposed a dedicated attribute
> "linker_input_section" instead of using the explicit section attribute.
> After discussions with Peter, I believe we don't need to introduce an
> additional attribute.
>
> Step 2: Symbol resolution in the linker
> =======================================
>
> The linker loads all bitcode...