public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: nathan@gcc.gnu.org To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nathan@gcc.gnu.org, yanliu@ca.ibm.com Subject: Re: c++/9433: [3.2/3.3/3.4 regression] SegFault in dynamic_cast Date: Tue, 28 Jan 2003 15:28:00 -0000 [thread overview] Message-ID: <20030128152851.1919.qmail@sources.redhat.com> (raw) Synopsis: [3.2/3.3/3.4 regression] SegFault in dynamic_cast State-Changed-From-To: analyzed->closed State-Changed-By: nathan State-Changed-When: Tue Jan 28 15:28:51 2003 State-Changed-Why: 2003-01-28 Nathan Sidwell <nathan@codesourcery.com> PR c++/9433 * libsupc++/tinfo.cc (__vmi_class_type_info::__do_dyncast): Cope with bases which are very ambiguous. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=9433
next reply other threads:[~2003-01-28 15:28 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-01-28 15:28 nathan [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-01-27 21:58 nathan 2003-01-24 15:22 bangerth
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=20030128152851.1919.qmail@sources.redhat.com \ --to=nathan@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ --cc=gcc-gnats@gcc.gnu.org \ --cc=gcc-prs@gcc.gnu.org \ --cc=yanliu@ca.ibm.com \ /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: linkBe 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).