On Wed, Apr 16, 2025 at 11:08 AM xionghuluo wrote:
>
> Hi, the bootstrap-lto-locality is much longer compared to boostrap-lto
> and bootstrap, and
>
> It seems that stage2 and stage3 only produced 5 partitions in LTO, is
> this reasonable...
Likely due to the high default of
-param=lto-max-local
Hi, the bootstrap-lto-locality is much longer compared to boostrap-lto
and bootstrap, and
It seems that stage2 and stage3 only produced 5 partitions in LTO, is
this reasonable...
Also could you please inform how much is the exact performance gain, please?
make bootstrap:
On Mon, Apr 14, 2025 at 3:11 PM Kyrylo Tkachov wrote:
>
> Hi Honza,
>
> > On 13 Apr 2025, at 23:19, Jan Hubicka wrote:
> >
> >> +@opindex fipa-reorder-for-locality
> >> +@item -fipa-reorder-for-locality
> >> +Group call chains close together in the binary layout to improve code code
> >> +localit
> On 15 Apr 2025, at 15:42, Richard Biener wrote:
>
> On Mon, Apr 14, 2025 at 3:11 PM Kyrylo Tkachov wrote:
>>
>> Hi Honza,
>>
>>> On 13 Apr 2025, at 23:19, Jan Hubicka wrote:
>>>
+@opindex fipa-reorder-for-locality
+@item -fipa-reorder-for-locality
+Group call chains close
Hi Honza,
> On 13 Apr 2025, at 23:19, Jan Hubicka wrote:
>
>> +@opindex fipa-reorder-for-locality
>> +@item -fipa-reorder-for-locality
>> +Group call chains close together in the binary layout to improve code code
>> +locality. This option is incompatible with an explicit
>> +@option{-flto-part
> +@opindex fipa-reorder-for-locality
> +@item -fipa-reorder-for-locality
> +Group call chains close together in the binary layout to improve code code
> +locality. This option is incompatible with an explicit
> +@option{-flto-partition=} option since it enforces a custom partitioning
> +scheme.
> On 26 Mar 2025, at 08:42, Kyrylo Tkachov wrote:
>
> Ping.
Ping.
https://gcc.gnu.org/pipermail/gcc-patches/2025-March/676958.html
I’ve ran a profiled LTO bootstrap of GCC with the new bootstrap-lto-locality
bootstrap config
And compared it against a GCC produced by the existing lto-bootstra
Ping.
Thanks,
Kyrill
> On 6 Mar 2025, at 09:25, Kyrylo Tkachov wrote:
>
> Hi all,
>
> Implement partitioning and cloning in the callgraph to help locality.
> A new -fipa-reorder-for-locality flag is used to enable this.
> The majority of the logic is in the new IPA pass in ipa-locality-cloning
