https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83294
--- Comment #3 from joseph at codesourcery dot com <joseph at codesourcery dot com> --- FWIW, current glibc already uses signed int for int32_t (via using it for __int32_t which is used to define int32_t), entirely as an accident following a header refactoring, but not for other types such as int_least32_t or int_fast32_t (so a glibc issue would still be appropriate for those other types).
