https://gcc.gnu.org/bugzilla/show_bug.cgi?id=28901
--- Comment #39 from Pekka <sarnila at adit dot fi> --- Well this change did now hit me. We have a code base of thousands of modules for a set of industrial systems. Every now and then we must recompile for new platforms with new versions of things like gcc. And now is one such time. The code base has been developed over 20 odd years and continues. Nearly every time some backward compatibility is broken it is a big headache for me. Some modules must be updated. Usually gcc warnings are very helpful in this. But now I get thousand of them. I our environment it is absolutely necessary to have version strings in every singe module to be stamped inside the created binary. Every module has it own versions. Modules are normally developed independently (a bit like kernel drivers). Years ago when 'unused warning' appeared we had this tedious project to add 'const' to every version stamp in every module (there are different version string names for different purposes). I must now figure out what is the best solution. There must be millions of C-modules out there that are still in current use and have versions or something similar stamped in they binaries. I see the need for progress but I must say I'm quite annoyed on how lightly in the open source world backward compatibility is broken.
