On 06.01.20 15:02, Wilco Dijkstra wrote: >> However, this is an undocumented change in the current NEWS, and seeing >>> literally hundreds of package failures, I doubt that's the right thing to >>> do, at >>> least without any deprecation warning first. Could that be handled, >>> deprecating >>> in GCC 10 first, and the changing that for GCC 11? > > This change was first proposed for GCC8, and rejected because of failures in > the > distros. Two years have passed, and there are still failures... Would this > change if > we postpone it even longer? My feeling is that nobody is going to actively > fix their > code if the default isn't changed first.
I think we were missing a proper announcement for GCC 8, and maybe we were not aware of the amount of code changes needed in third party packages. So maybe we should have had in GCC 8 a configure option to make that the default behavior, announce it in the release notes, ask for testing using that option, and do the defaults change in GCC 9. We could do that for GCC 10/11, or just bite in the apple and now fix all packages builds. Matthias
