search for: hotcallsitethreshold

Hello, My team and I noticed that callsite hotness information is not preserved from compile to link step with LTO/thinLTO enabled. As a result, the link step inlining pass remains conservative when inlining callsites known to be hot (ie. without the 'HotCallSiteThreshold' which is set at 3000 by default). There are likely many cross-module inlining opportunities lost this way, and diminishes the benefit of using LTO/thinLTO+PGO together. In general, does LLVM pass profiling information through the IR to the link step other than branch probabilities and functi...

...dev at lists.llvm.org> wrote: Hello, My team and I noticed that callsite hotness information is not preserved from compile to link step with LTO/thinLTO enabled. As a result, the link step inlining pass remains conservative when inlining callsites known to be hot (ie. without the 'HotCallSiteThreshold' which is set at 3000 by default). There are likely many cross-module inlining opportunities lost this way, and diminishes the benefit of using LTO/thinLTO+PGO together. The callsite hotness is passed via the IR, so it should be there in the LTO/ThinLTO backends (during the link step). C...

...t; >> My team and I noticed that callsite hotness information is not >> preserved from compile to link step with LTO/thinLTO enabled. As a result, >> the link step inlining pass remains conservative when inlining callsites >> known to be hot (ie. without the 'HotCallSiteThreshold' which is set at >> 3000 by default). There are likely many cross-module inlining opportunities >> lost this way, and diminishes the benefit of using LTO/thinLTO+PGO together. >> >> >> >> The callsite hotness is passed via the IR, so it should be there...

...My team and I noticed that callsite hotness information is not preserved from compile to link step with LTO/thinLTO enabled. As a result, the link step inlining pass remains conservative when inlining callsites known to be hot (ie. without the 'HotCallSiteThreshold' which is set at 3000 by default). There are likely many cross-module inlining opportunities lost this way, and diminishes the benefit of using LTO/thinLTO+PGO together. The callsite hotness is passed via the IR, so it should be there in the LTO/Thin...