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: "paolo.carlini at oracle dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Thu, 4 Aug 2011 15:34:13 +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 #110 from Paolo Carlini <paolo.carlini at oracle dot com> 2011-08-04 15:29:58 UTC ---
> 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.
This is very, very good, thanks.
> > 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.
I think we really need some feedback from Rainer, then. Sorry, but it's the
first time I see the mangling machinery at issue only for a specific target. At
some point we'll have to involve the front-end people anyway, because the code
lives in cp/.
> 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...
Ok.
> 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?
Rainer?