http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56306
--- Comment #2 from Jonathan Wakely <redi at gcc dot gnu.org> 2013-02-13 12:22:19 UTC --- GCC can obviously alter its internal include paths to its own headers because it knows what they contain and how to find the contents. It can't possibly know about arbitrary non-GCC paths or whether it's correct or safe to append "32" to those paths.
