On Fri, Jan 10, 2025 at 12:23:42PM -0700, Simon Glass wrote:
Hi Tom,
On Fri, 10 Jan 2025 at 09:17, Tom Rini trini@konsulko.com wrote:
[snip]
It be great if buildman size comparison had some way to csv the output. That's what's missing imo from being able to have some automation or even just nicer tooling.
What sort of tooling could we have? I would like something in CI which reports code-size changes in a useful way, perhaps failing if the delta is too large for more than x boards. WDYT?
I don't want it making automated decisions (for example when platforms enable features they grow, a lot, on purpose) but generating an output that can be imported elsewhere would be good. I want something that can be thrown in a database (or added to a database). Setting aside the challenge of LTO, and looking at what I see in a recent before/after, it would be good to query and see that for ~60 platforms mpc8xxx_gpio_probe grew by 44 bytes. Which platforms that is only matters if it's not clear from the log which commit that's likely from.