* Sam James: >> Has anyone performed experiments to determine the impact of this change >> on typical free software distributions? > > I filed https://gcc.gnu.org/PR117298 for an issue Joseph noticed in one > of the GCC tests (that is actually an improvement, but a missed opt for > older standards). I haven't done any sort of testing but am curious > about it as well. > > I could do such a test for code size en-masse (and perhaps maybe even > check where the image changed at all). Runtime performance is far harder > for me to do at scale though. We can use significant code size changes > as a proxy for interesting candidates to investigate though. > > What are you thinking of?
Mostly compatibility with older configure scripts. There are the new keywords bool/true/false, and the -Werror=deprecated-non-prototype default that could alter configure test outcomes. Maybe there's something else I'm missing? Some estimate of the build failure would also be helpful. Is it the same as, e.g. the GCC 12 to GCC 13 update, or is it igher? Thanks, Florian
