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:38:58 +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 #111 from Marc Glisse <marc.glisse at normalesup dot org> 2011-08-04 15:38:52 UTC ---
(In reply to comment #110)
> > 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/.
Well, it's not everyday you move struct tm from the global namespace to
namespace std... I can't think of many ways to keep binary compatibility with
such a change, except through mangling. And I don't think people would be happy
if we broke binary compatibility on Solaris just so we can set __cplusplus.
More fixinclude doesn't sound very good either.