This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug libstdc++/1773] __cplusplus defined to 1, should be 199711L
- From: "marc.glisse at normalesup dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Thu, 4 Aug 2011 15:24:47 +0000
- Subject: [Bug libstdc++/1773] __cplusplus defined to 1, should be 199711L
- Auto-submitted: auto-generated
- References: <bug-1773-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=1773
--- Comment #109 from Marc Glisse <marc.glisse at normalesup dot org> 2011-08-04 15:21:36 UTC ---
(In reply to comment #108)
> Excellent. Can we sort out separately with C++ front-end people like Jason this
> mangling (and demangling too, I suppose) issue?
Yes. There are independent pieces:
*fixincludes
*libstdc++
*mangling
and libcpp is the big red button that can only be pressed at the end. None of
the changes should have any noticable effect as long as we haven't pressed the
red button.
> If I understand correctly it's
> something which we are going to need for C++11 anyway, right?
Ah, no. It is something we only need if we want to keep binary compatibility
between __cplusplus=1 and __cplusplus=199711L binaries on Solaris. As soon as
we break the ABI (libstdc++-v7?), it should be reverted as useless.
About demangling, I don't know if we wan't to change it (and it would have to
be Solaris-only). std::tm will be printed as tm, but that doesn't seem so
bad...
PS: wasn't there a discussion some time ago about adding macros like
__SunOS_5_10 (name taken from sunpro) so we can detect the Solaris version?