public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Aaron W. LaFramboise" <aaronavay62@aaronwl.com>
To: Danny Smith <dannysmith@users.sourceforge.net>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>, Christopher Faylor <me@cgf.cx>
Subject: Re: [Patch} Fix dynamic casts across dll boundaries on windows targets
Date: Thu, 21 Oct 2004 03:59:00 -0000	[thread overview]
Message-ID: <417733A6.6010101@aaronwl.com> (raw)
In-Reply-To: <000601c4b5c4$017f8b90$b64861cb@DANNY>

Danny Smith wrote:

> One of the problems with RTTI vs dllimport is that dllimported objects
> do not have a constant address at compile time. This creates a problem
> for static initialisation of,  say, another RTTI object or a vtable
> that has a
> dllimported typeinfo member.

Does autoimport or the pseudo-relocator help with this?

Aaron W. LaFramboise

      reply	other threads:[~2004-10-21  3:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-16  9:47 Danny Smith
2004-10-17 22:25 ` Christopher Faylor
2004-10-19  6:21 ` Aaron W. LaFramboise
2004-10-19 10:52   ` Danny Smith
2004-10-21  3:59     ` Aaron W. LaFramboise [this message]

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=417733A6.6010101@aaronwl.com \
    --to=aaronavay62@aaronwl.com \
    --cc=dannysmith@users.sourceforge.net \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=me@cgf.cx \
    /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).