* C++ headers vs safe-ctype.h
@ 2014-11-07 8:53 FX
0 siblings, 0 replies; only message in thread
From: FX @ 2014-11-07 8:53 UTC (permalink / raw)
To: GCC Development; +Cc: ilya.enkovich
Hi,
We are currently seeing two cases of C++-related bootstrap failures on Darwin, due to C++ header <string> being included after “system.h” and “safe-ctype.h”: <string> headers, on Darwin, use ctype macros which GCC poisons through safe-ctype.h
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63703
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63750
This triggers in libcc1, and in the new ipa-chkp.c file. We can move the #include <string> line higher in the source files (as is already done, e.g., in go/go-system.h), but we probably need to think of a global solution, such as including basic C++ headers directly from the system.h header. I do not know enough about the state of our mixed C/C++ build to understand if that would work or create chaos, so I’m dropping a line here so that “awareness of this general issue is raised”, as they say rather pompously :)
Cheers,
FX
PS: Ilya, I tried to CC you on the bugzilla PR 63750, but you’re not in the database.
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2014-11-07 8:53 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2014-11-07 8:53 C++ headers vs safe-ctype.h FX
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).