This is the mail archive of the
libstdc++@gcc.gnu.org
mailing list for the libstdc++ project.
Re: libstdc++-v3 and GCC 2.95.3
- To: Joe Buck <jbuck at synopsys dot COM>, pedwards at disaster dot jaj dot com (Phil Edwards)
- Subject: Re: libstdc++-v3 and GCC 2.95.3
- From: Benjamin Scherrey <scherrey at innoverse dot com>
- Date: Wed, 11 Apr 2001 22:58:15 -0400
- Cc: KWilliams at visionael dot com (Kevin Williams), libstdc++ at gcc dot gnu dot org ('libstdc++ at gcc dot gnu dot org')
- Organization: Innoverse, Inc.
- References: <200104111643.JAA05298@toledo.synopsys.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Sorry to disturb you but I've got some template-intensive code that performs
a perfectly legal (I believe) dynamic_cast inside it that fails to build
under 2.95.3 but runs perfectly nicely under 2.95.2. Worse still, the error
message makes no sense because it claims I can't cast to the template type
that is its natural type upon instantiation. I haven't had the time to
investigate it properly nor reproduce it in something even remotely postable
so I can't say for sure what the problem is. I could see similar issues (type
confusion in templates) being hit in the STL.
regards & later,
Ben Scherrey
On Wednesday 11 April 2001 12:43 pm, Joe Buck wrote:
> I would be amazed (and disturbed) if there is code that builds with
> 2.95.2 and not 2.95.3. The latter is only a few small bug fixes with
> respect to the former, with a lot of attention paid to binary
> compatibility.
-----BEGIN PGP SIGNATURE-----
Version: PGP 6.5.8
iQA/AwUBOtUZymj9nzX41wUgEQJFKQCeJVQCkKkk7wa64vD5BFKEszYlI9IAni8+
ctiU2wNSHTJkUlbTttnQraxy
=sTAN
-----END PGP SIGNATURE-----