From: Nathan Sidwell <nathan@codesourcery.com>
To: "John (Eljay) Love-Jensen" <eljay@adobe.com>
Cc: MSX to GCC <gcc-help@gcc.gnu.org>
Subject: Re: typeinfo problem (bug?)
Date: Mon, 27 Nov 2006 10:07:00 -0000 [thread overview]
Message-ID: <456AB905.6060507@codesourcery.com> (raw)
In-Reply-To: <EDC8DDD212FEB34C884CBB0EE8EC2D91216645@namailgen.corp.adobe.com>
John (Eljay) Love-Jensen wrote:
> Hi everyone,
>
> I've run into a problem with std::type_info.
>
> It appears that hidden visibility can cause multiple instances of a type_info object for one type, hence RTTI information is not being merged across SSO and DSO boundaries. :-(
Example? At first blush it might be the exact intended behaviour. If you've
made a type hidden, why would you expect it to be visible?
nathan
--
Nathan Sidwell :: http://www.codesourcery.com :: CodeSourcery
nathan@codesourcery.com :: http://www.planetfall.pwp.blueyonder.co.uk
next prev parent reply other threads:[~2006-11-27 10:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-24 19:01 John (Eljay) Love-Jensen
2006-11-27 10:07 ` Nathan Sidwell [this message]
2006-11-27 13:05 ` John Love-Jensen
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=456AB905.6060507@codesourcery.com \
--to=nathan@codesourcery.com \
--cc=eljay@adobe.com \
--cc=gcc-help@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).