[PATCH v3 2/2] ci: Add a test for a non-LTO build

[Simon Glass]

Hi Tom,

On Mon, 8 Aug 2022 at 10:09, Tom Rini <trini at konsulko.com> wrote:
>
> On Sun, Aug 07, 2022 at 09:48:01AM -0600, Simon Glass wrote:
> > Hi Tom,
> >
> > On Wed, 3 Aug 2022 at 12:13, Simon Glass <sjg at chromium.org> wrote:
> > >
> > > Check that sandbox builds and runs tests OK with LTO disabled.
> > >
> > > Signed-off-by: Simon Glass <sjg at chromium.org>
> > > ---
> > >
> > > (no changes since v1)
> > >
> > >  .azure-pipelines.yml | 4 ++++
> > >  .gitlab-ci.yml       | 7 +++++++
> > >  2 files changed, 11 insertions(+)
> > >
> >
> > Another little snippet - it seems that CI performance for the world
> > builds has dropped 20% - 30% with LTO enabled. With tui I used to see
> > just over 1 build a second; now it is running at about 0.78 and kaki
> > has gone from close to 0.5 to 0.29.
> >
> > I wonder if ,in CI, we should just build a selection of boards with
> > LTO, switching the world builds to non-LTO? The problem is that we may
> > hit code size limits in SPL.
>
> I'm not sure how you're measuring this. We don't enable LTO by default
> anywhere other than sandbox, it's opt-in for a few platforms still.

I just assumed that is why, since it slows incremental builds down so
much. But perhaps something else is going on? I can try to bisect it,
I suppose, if I take tui offline for a bit.

Regards,
Simon