This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c++/28687] [4.2 regression] dynamic_cast<void*> disallowed too rigorously with -fno-rtti
- From: "pkasting at google dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 22 Aug 2006 20:31:19 -0000
- Subject: [Bug c++/28687] [4.2 regression] dynamic_cast<void*> disallowed too rigorously with -fno-rtti
- References: <bug-28687-11332@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #16 from pkasting at google dot com 2006-08-22 20:31 -------
Comment 4 seems to make it clear that GCC's current behavior differs from past
behavior that was legal under the spec. I fail to see the utility of the
current behavior or why it would be objectionable to apply the patch on this
bug.
(In reply to comment #12)
> | I'm not claiming that the behavior isn't conformant to the docs, I'm claiming
> | that you regressed a construct
>
> No, we did not regress because the documentation was very explicit.
The documentation was previously incorrect. The compiler was changed to match
the documentation's behavior, rather than the documentation being changed to
match the compiler's behavior and the C++ standard. The patch on this bug
makes the IMO correct fix of keeping the compiler behavior and documentation in
sync, but making them match the old, standards-compliant behavior that existing
products rely on.
This bug should be REOPENED.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28687