https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105935
Francois-Xavier Coudert <fxcoudert at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |fxcoudert at gcc dot gnu.org
--- Comment #1 from Francois-Xavier Coudert <fxcoudert at gcc dot gnu.org> ---
Created attachment 55363
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=55363&action=edit
Proposed patch
The issue is real, but I would suggest that snprintf() and vsnprintf() should
always be available, being C99 functions, on our targets. The real trigger for
your issue in a mingw-w64 bug, if I read that right.
I would simply recommend we stop providing our own, unsafe workarounds for
these functions, per the patch attached (needs regenerating in maintainer mode,
on top of the patch file).
