https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88993
--- Comment #5 from Martin Sebor <msebor at gcc dot gnu.org> --- For some background into the source of the limit see the discussion below: https://gcc.gnu.org/ml/gcc-patches/2016-08/msg01772.html The warning is based on the C limit in the discussion and the Glibc bug/limitation discussed in it. I certainly agree with making Glibc's sprintf more robust by avoiding dynamic memory allocation but that (unfortunately) won't let GCC remove the limit. I'm open to adjusting the warning to make it more useful if it's causing trouble. It's not clear to me yet that it is causing enough trouble to justify making a change to it at this stage of GCC development. Richard, can you give us an idea of how much trouble this is causing and what the impact would be of not suppressing it in GCC 9?
