------- Comment #18 from mmitchel at gcc dot gnu dot org 2010-02-18 15:13 ------- Paolo --
I think libsupc++ is just as much a "system library" as libstdc++. It doesn't have an ISO-standard API, of course, but that's not the point; it's just as much a part of the system/implementation as libstdc++. To the extent a program is going to use a header that we ship from libsupc++, that program certainly doesn't want to get random warnings about those headers. However, Julian Brown warns me that he's been playing with this and that it doesn't entirely solve the problem. It may be that my earlier patch to arm.c is insufficient in some cases. So, I'd like the libstdc++ maintainers to make the change to the libsupc++ headers -- unless someone can articulate a good reason not to do so of course -- but there may still be more work to do. We will continue to investigate the possible non-workingness of the patch. Thanks, -- Mark -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42748
