search for: function_reordering_plugin

On Mon, Jan 16, 2017 at 12:31 PM, Sean Silva via llvm-dev <llvm-dev at lists.llvm.org> wrote: > Do we have any open projects on LLD? > > I know we usually try to avoid any big "projects" and mainly add/fix things > in response to user needs, but just wondering if somebody has any ideas. > I'm not particularly active in lld anymore, but the last big item I'd

...It looks like the current gcc plugin calls back into gcc for the actual layout algorithm itself (function call find_pettis_hansen_function_layout) rather than the reordering logic living in the linker: https://android.googlesource.com/toolchain/gcc/+/3f73d6ef90458b45bbbb33ef4c2b174d4662a22d/gcc-4.6/function_reordering_plugin/function_reordering_plugin.c <https://android.googlesource.com/toolchain/gcc/+/3f73d6ef90458b45bbbb33ef4c2b174d4662a22d/gcc-4.6/function_reordering_plugin/function_reordering_plugin.c> I was thinking about this: could this be done by reorganizing the module itself for LTO? That wouldn’t help...

...t) rather than the reordering >>>>> logic living >>>>> > in the linker: >>>>> > https://android.googlesource.com/toolchain/gcc/+/3f73d6ef904 >>>>> 58b45bbbb33ef4c2b174d4662a22d/gcc-4.6/function_reordering_pl >>>>> ugin/function_reordering_plugin.c >>>>> > >>>>> > >>>>> > I was thinking about this: could this be done by reorganizing the >>>>> module >>>>> > itself for LTO? >>>>> > >>>>> > That wouldn’t help non-LTO and...

...ls back into gcc for > > the actual layout algorithm itself (function call > > find_pettis_hansen_function_layout) rather than the reordering logic living > > in the linker: > > https://android.googlesource.com/toolchain/gcc/+/3f73d6ef90458b45bbbb33ef4c2b174d4662a22d/gcc-4.6/function_reordering_plugin/function_reordering_plugin.c <https://android.googlesource.com/toolchain/gcc/+/3f73d6ef90458b45bbbb33ef4c2b174d4662a22d/gcc-4.6/function_reordering_plugin/function_reordering_plugin.c> > > > > > > I was thinking about this: could this be done by reorganizing the module >...

...yout algorithm itself (function call > > find_pettis_hansen_function_layout) rather than the reordering logic > living > > in the linker: > > https://android.googlesource.com/toolchain/gcc/+/ > 3f73d6ef90458b45bbbb33ef4c2b174d4662a22d/gcc-4.6/function_ > reordering_plugin/function_reordering_plugin.c > > > > > > I was thinking about this: could this be done by reorganizing the module > > itself for LTO? > > > > That wouldn’t help non-LTO and ThinLTO though. > > This is a dimension that I think can be explored. The fact that it > wouldn't help w...

...; > find_pettis_hansen_function_layout) rather than the reordering logic >>> living >>> > in the linker: >>> > https://android.googlesource.com/toolchain/gcc/+/3f73d6ef904 >>> 58b45bbbb33ef4c2b174d4662a22d/gcc-4.6/function_reordering_pl >>> ugin/function_reordering_plugin.c >>> > >>> > >>> > I was thinking about this: could this be done by reorganizing the >>> module >>> > itself for LTO? >>> > >>> > That wouldn’t help non-LTO and ThinLTO though. >>> >>> This is a dime...