btashton commented on issue #2425: URL: https://github.com/apache/incubator-nuttx/issues/2425#issuecomment-735213180
> It adds a tremendous level of understanding to the cause and effect of the changes in the release. It would make sense to run bloaty on some representative config's in the PR. > Here is a thought on how to present it: We could have some config permutations just for size comparison. We would enable everything (we can) and have a `bloaty.ld` linker scripts with multi Megs of memory, so we can always link. Of course these configs would need a disclaimer not to use them. That is actually an interesting thought. I was already looking at possibly adding some configurations that are very feature heavy to make it easier to get some more build coverage as well. I have a configuration that I use locally on one of the STM32 with a lot of ram/flash that has net/usb/adc/sensors/display/etc... all enabled which also makes it easier for me to do functional testing without having to spend so much time flashing everything. There are other boards like the imxrt where we could get create some functional large configurations. I spent some time putting some more tooling together and I think I have an idea on how to go about adding some useful visualization to this so I'll share something early next week. We actually already have over 250 runs against commits merged in the master branch each with around 590 builds collected and that is only since the end of October, so I suspect I can show some interesting graphs from that. ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
