search for: outputsectionid

...enting an overlay. > It's not so much about other modules (files) - you could have multiple files contributing input sections to the same overlay, for instance, and you would want to optimize across them. But you wouldn't want to de-duplicate a constant from another overlay. I think the OutputSectionID-as-optimization-domain idea captures this use case, no? - Linker can omit the output section information for sections that the > user doesn't care where they go, and let the linker decide based on > some size constraint later. That's an interesting idea to allow a 'don't ca...

Hello Tobias, Thanks very much for the RFC, I think that this will be useful in persuading embedded developers to use LTO in their projects. I think the overall approach for communication between the linker and code generator sounds reasonable. I've got some questions/comments based on some experience with Arm's proprietary linker, which supports LTO but has a different linker script

RFC: (Thin)LTO with Linker Scripts At the last US LLVM Developers' Meeting, we presented [1] a proposal for linker script support in (Thin)LTO. In this RFC, I would like to describe the proposal in more detail and invite the community's feedback, so we can build consensus on the upstream implementation. The end goal of this effort is to extend the benefits of (Thin)LTO, including