public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bgreen at nas dot nasa dot gov" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/11247] -frepo fails to instantiate typeinfo
Date: Fri, 31 Dec 2004 00:14:00 -0000 [thread overview]
Message-ID: <20041231001410.4458.qmail@sourceware.org> (raw)
In-Reply-To: <20030618234434.11247.bgreen@nas.nasa.gov>
------- Additional Comments From bgreen at nas dot nasa dot gov 2004-12-31 00:14 -------
I just discovered this bug still exists, in a slightly changed guise.
The previously submitted code now compiles, but a minor change brings the bug
right back.
Attached is the new version of the code that produces the bug.
The diff is essentially this:
< dynamic_cast<IType<int>*>(p);
> IType<int> *p2 = dynamic_cast<IType<int>*>(p);
I'm currently using Gentoo's g++ version 3.4.3.
g++ (GCC) 3.4.3 20041125 (Gentoo Linux 3.4.3-r1, ssp-3.4.3-0, pie-8.7.7)
--
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|FIXED |
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11247
next prev parent reply other threads:[~2004-12-31 0:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-18 23:44 [Bug c++/11247] New: " bgreen at nas dot nasa dot gov
2003-06-19 13:47 ` [Bug c++/11247] " bangerth at dealii dot org
2003-07-29 16:33 ` pinskia at physics dot uc dot edu
2003-09-02 20:14 ` bgreen at nas dot nasa dot gov
2004-08-16 18:25 ` bangerth at dealii dot org
2004-08-25 17:02 ` pinskia at gcc dot gnu dot org
2004-12-31 0:14 ` bgreen at nas dot nasa dot gov [this message]
2005-01-31 6:57 ` pinskia at gcc dot gnu dot org
[not found] <bug-11247-1825@http.gcc.gnu.org/bugzilla/>
2007-06-14 22:32 ` aaw at gcc dot gnu dot org
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20041231001410.4458.qmail@sourceware.org \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).