http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52974
--- Comment #2 from Manuel López-Ibáñez <manu at gcc dot gnu.org> 2012-04-13 13:42:51 UTC --- (In reply to comment #0) > This probably isn't a good idea for user headers, as the include path they use > with -I should be preserved so they recognise it, but for GCC's own C++ > headers > (and possibly all system headers?) it would be a huge improvement. System headers are easy to detect, but what is "GCC's own C++ headers"? How can one detect those?
