------- Comment #18 from paolo dot carlini at oracle dot com 2009-04-06 14:13 ------- (In reply to comment #17) > Superficially, it looks as if it fails because stdint.h isn't picked up > properly by libstdc++ (in contrast to the C test-suite) so I do think this is > worthwhile. I don't think it's worthwhile to try and make a distinction > between incomplete-target-stdint and libstdc++-stdint-include-issues before > that analysis. :)
I see what you mean, but one thing is configure time, another the library proper. Again, when 448 will closed, the library will be cleaned up to not do *any* configure time checks in this area. Otherwise, <cstdint>, as you can see yourself is *trivial*, cannot do anything wrong with stdint.h, as <cfloat> doesn't do anything wrong with float.h. That said, if you notice something strange just let us know! -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39644
