public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: aoliva@gcc.gnu.org To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, hubbard@ilm.com, jyost@ilm.com, kainz@ilm.com, nobody@gcc.gnu.org Subject: Re: libstdc++/4292: dynamic_cast incorrectly returns 0 Date: Fri, 28 Sep 2001 20:34:00 -0000 [thread overview] Message-ID: <20010929033401.14446.qmail@sourceware.cygnus.com> (raw) Synopsis: dynamic_cast incorrectly returns 0 State-Changed-From-To: open->analyzed State-Changed-By: aoliva State-Changed-When: Fri Sep 28 20:34:00 2001 State-Changed-Why: RTLD_GLOBAL should fix the problem. I'm not sure we really want to make type comparison less efficient to allow for non-GLOBAL dlopening. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view&pr=4292&database=gcc
next reply other threads:[~2001-09-28 20:34 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2001-09-28 20:34 aoliva [this message] -- strict thread matches above, loose matches on Subject: below -- 2001-09-10 16:06 kainz
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=20010929033401.14446.qmail@sourceware.cygnus.com \ --to=aoliva@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ --cc=gcc-prs@gcc.gnu.org \ --cc=hubbard@ilm.com \ --cc=jyost@ilm.com \ --cc=kainz@ilm.com \ --cc=nobody@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: 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).