[Bug target/37727] New: NO_IMPLICIT_EXTERN_C for newlib
jifl-bugzilla at jifvik dot org
gcc-bugzilla@gcc.gnu.org
Fri Oct 3 16:23:00 GMT 2008
Is there any reason that NO_IMPLICIT_EXTERN_C can't be automatically defined,
if --with-newlib is used? newlib's headers are C++-safe.
--
Summary: NO_IMPLICIT_EXTERN_C for newlib
Product: gcc
Version: 4.3.2
Status: UNCONFIRMED
Severity: trivial
Priority: P3
Component: target
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: jifl-bugzilla at jifvik dot org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37727
More information about the Gcc-bugs
mailing list