On 11/13/25 6:57 PM, Tom Rini wrote: Hello Tom,
So, taking a look at the test branch you pointed me at, my big concern is size growth. On imx8mp_dhcom_drc02 (where we're already LTO'ing), with the CI gcc-14.2.0 toolchain full U-Boot grows by more than 6KiB and SPL by a bit more than 2KiB. This is a bit of a worst-case, imx8mp_navqp is a bit more than 3KiB / 548 bytes, with the average feeling like ~4KiB/1KiB for aarch64.
Do you know why this growth happened ? Is that in libfdt ? How did you find it ?
[...]
Rather than a full-resync for the last time we needed a feature found upstream.
I really don't want to do partial resync, it will only make it harder to maintain obsolete code base going forward. Even this resync was hard due to that exact current divergence.
There are things we *need* like to be 8-byte aligned and also the phandle resolution thing I believe inspired your investigations here, but I don't know if we can take the whole sync. Or maybe needing to work with upstream to shrink down some parts, I'm unsure.
CI does show that no boards went oversize . If there is some growth on existing devices, maybe we can shrink that, but maintaining obsolete DTC code base going forward and picking random updates into it, that will only lead to increasing maintenance pain, so I don't want to do that.
-- Best regards, Marek Vasut
