https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85995
--- Comment #5 from joseph at codesourcery dot com ---
On Fri, 1 Jun 2018, vincent-gcc at vinc17 dot net wrote:
> Programmers normally use conditionals on '__STDC__' to ask whether
> it is safe to use certain features of ISO C, such as
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85995
--- Comment #4 from Vincent Lefèvre ---
(In reply to jos...@codesourcery.com from comment #3)
> See trouble.texi, "Non-bugs" / "Certain Changes We Don't Want to Make",
> "Undefining @code{__STDC__} when @option{-ansi} is not used."
which answer
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85995
--- Comment #3 from joseph at codesourcery dot com ---
See trouble.texi, "Non-bugs" / "Certain Changes We Don't Want to Make",
"Undefining @code{__STDC__} when @option{-ansi} is not used." (and the
description of handling of base standards in i
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85995
--- Comment #2 from Vincent Lefèvre ---
I don't see the point of defining both __STDC__ and __STDC_VERSION__ if GCC
cannot guarantee anything about standard conformance. With the current state,
it is not possible to test these macros in order to
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85995
--- Comment #1 from Richard Biener ---
I guess that would break way more code than the current state (or force people
to use -std=cXX over -std=gnuXX).
