From: Dirk Mueller <dmuell@gmx.net>
To: Joe Buck <jbuck@synopsys.COM>
Cc: Waldo Bastian <bastian@kde.org>,
kde-core-devel@mail.kde.org, gcc@gcc.gnu.org
Subject: Re: KDE hackers, please read (was [nathan@codesourcery.com: Re: GCC 3.0.3: Bugs to Fix]) (fwd)
Date: Tue, 04 Dec 2001 16:37:00 -0000 [thread overview]
Message-ID: <20011205013551.A8087@rotes20.wohnheim.uni-kl.de> (raw)
In-Reply-To: <200112042250.OAA02613@atrus.synopsys.com>
On Die, 04 Dez 2001, Joe Buck wrote:
> But that causes an interesting problem. You say that you don't want to
> use RTLD_GLOBAL because someone might duplicate a class name (say,
> "DisplayList"). Of course, this violates the one-definition rule, but
> let's ignore that for a moment.
Point taken for the RTLD_GLOBAL part, but why do we need RTLD_NOW in order
to make RTTI work, as the original posting pointed out ?
I think lazy symbol resolving is the least thing an ABI should be capable of
when living in the 21th century..
Dirk
next prev parent reply other threads:[~2001-12-05 0:37 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.42.0112041339390.30216-110000@bochum.stuttgart.redhat.com>
2001-12-04 13:21 ` Waldo Bastian
2001-12-04 13:29 ` shaheed
2001-12-04 14:51 ` Joe Buck
2001-12-04 16:37 ` Dirk Mueller [this message]
2001-12-05 12:16 ` Mark Mitchell
2001-12-09 23:58 ` Waldo Bastian
2001-12-10 0:52 ` Simon Hausmann
2001-12-10 2:45 ` Lubos Lunak
2001-12-10 9:55 ` Mark Mitchell
2001-12-10 11:16 ` KDE hackers, please read (was [nathan@codesourcery.com: Re: GCC Joe Buck
2001-12-10 11:39 ` Mark Mitchell
2001-12-10 11:47 ` Joe Buck
2001-12-11 13:00 ` KDE hackers, please read (was [nathan@codesourcery.com: Re: GCC 3.0.3: Bugs to Fix]) (fwd) Alexandre Oliva
2001-12-11 9:28 ` Mark Mitchell
2001-12-10 1:33 ` Richard Henderson
2001-12-10 2:41 ` Andreas Schwab
2001-12-10 2:07 ` Nathan Sidwell
2001-12-10 3:01 ` Jakub Jelinek
2001-12-05 1:23 ` Nathan Sidwell
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=20011205013551.A8087@rotes20.wohnheim.uni-kl.de \
--to=dmuell@gmx.net \
--cc=bastian@kde.org \
--cc=gcc@gcc.gnu.org \
--cc=jbuck@synopsys.COM \
--cc=kde-core-devel@mail.kde.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).