On Thu, Jun 8, 2023 at 11:15 AM Jakub Jelinek via Gcc-patches
wrote:
>
> On Thu, Jun 08, 2023 at 10:05:43AM +0100, Jonathan Wakely via Gcc-patches
> wrote:
> > > Looking at assembly, one of the differences I see is that the "after"
> > > version has calls to realloc_insert(), while "before"
On Thu, 8 Jun 2023 at 09:58, Maxim Kuvyrkov
wrote:
> Hi Jonathan,
>
> Interestingly, this increases code-size of -O3 code on aarch64-linux-gnu
> on SPEC CPU2017's 641.leela_s benchmark [1].
>
> In particular, FastBoard::get_nearby_enemies() grew from 1444 to 2212
> bytes. This seems like a
On Thu, Jun 08, 2023 at 10:05:43AM +0100, Jonathan Wakely via Gcc-patches wrote:
> > Looking at assembly, one of the differences I see is that the "after"
> > version has calls to realloc_insert(), while "before" version seems to have
> > them inlined [2].
> >
> > [1]
> >
On Thu, 8 Jun 2023 at 09:58, Maxim Kuvyrkov
wrote:
> Hi Jonathan,
>
> Interestingly, this increases code-size of -O3 code on aarch64-linux-gnu
> on SPEC CPU2017's 641.leela_s benchmark [1].
>
> In particular, FastBoard::get_nearby_enemies() grew from 1444 to 2212
> bytes. This seems like a
Hi Jonathan,
Interestingly, this increases code-size of -O3 code on aarch64-linux-gnu on
SPEC CPU2017's 641.leela_s benchmark [1].
In particular, FastBoard::get_nearby_enemies() grew from 1444 to 2212 bytes.
This seems like a corner-case; the rest of SPEC CPU2017 is, mostly, neutral to
this
