Hi, I was under impression that BSS section just declares a size of memory to allocate on start without actually saving any data to the result binary.
For example:
should not affect the result binary size. However, that's not the case for my code, 1000 zeros are added to the result. I also tried to explicitly define the section:
I think BSS has always been included in the binary unless a ROM is being generated.
For RAM compiles I can see why it's annoying. I have a hunch that adding an option to do as you're doing may cause issues for some classic platforms: in particular those ones that rearrange the binary on load to resolve paging conflicts which I'd need to check out before officially adding this feature.
If you just make it optional (and NOT default) then it's probably fine.
I'm certainly not planning to use this feature, how well intentioned that may be. The tap filesize is the only way I have, to see how large the loading part is, I'd rather not want to sacrifice it.