Hey Marius,

> Maybe file a different bug report for those so it does not get
> forgotten?  One thing at the time...

Ok!

> FWIW I think the original problem with huge closure increase has been
> fixed with 8e98f750e63e8723db0361f4e3e960193278fa47 and
> 7688dbbdd7a7a091c9a0fc4850e70725e3ff64e3.
>
> I'm getting 1372 MiB for the cross-mini example at approximately commit
> d594963856690f1aacf228c8a83e406d33bc44ce (cross-built for
> arm-linux-gnueabihf).

What's cross-mini? On commit d594963856690f1aacf228c8a83e406d33bc44ce of
core-updates (both patches you mentionned included), I still have a
1.9GiB closure.

Note, that applying the "lib" output patch, it drops down to 1.6GiB,
which is good news :).

> The patch is almost 40k lines!  Most of the changes are whitespace
> changes in the ChangeLog files, could you remove the commit log and
> ChangeLog entries altogether to make the patch easier to parse?
>
> Where did you find this patch?

You'll find a trimmed patch attached. I found the GCC patch upstream
(pushed in January), after finding the option in the online manual.

Thanks,

Mathieu