------- Comment #24 from paolo dot carlini at oracle dot com 2009-04-08 07:39 ------- Interesting. Actually, I seem to remember that for some time we didn't have specific lines in the configure test checking those macros and that led to unespected fails in the testsuite for some targets which, unexpectedly had everything in stdint.h but those required macros, exactly as you are saying. I would suggest looking in the Changelog for a change of mine tightening that check (thus, touching acinclude). In case, I think you should point out the problem to the people responsible for the newlib bits of 448, because of course target libraries assuming stdint.h unconditionally available also assume the standard conforming behavior for the macros. In fact, I hope I'm wrong, but the last days I saw some checkins around for the other OSes and I didn't notice the macros and the machinery using the feature macro...
One last remark, for the record: for C++0x we eventually want those macros unconditionally available irrespective of the C99 feature macro, thus we'll probably have to tweak the GCC machinery in that sense, with a bit of preprocessing directives on top of stdint.h checking the C++ dialect -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39644