This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Duplicate data objects in shared libraries

From: Jason Merrill <jason at redhat dot com>
To: Mark Mitchell <mark at codesourcery dot com>
Cc: "Martin v. Loewis" <martin at v dot loewis dot de>,David Abrahams <david dot abrahams at rcn dot com>,"H . J . Lu" <hjl at lucon dot org>,"drepper at redhat dot com" <drepper at redhat dot com>,"Ralf W. Grosse-Kunstleve" <rwgk at cci dot lbl dot gov>,"gcc at gcc dot gnu dot org" <gcc at gcc dot gnu dot org>
Date: Mon, 20 May 2002 20:39:51 +0100
Subject: Re: Duplicate data objects in shared libraries
References: <76260000.1021912729@warlock.codesourcery.com><wvlhel2ocz3.fsf@prospero.cambridge.redhat.com><60630000.1021922077@gandalf.codesourcery.com>

>>>>> "Mark" == Mark Mitchell <mark@codesourcery.com> writes:

> I think that the ABI specifies the name -- even for the local class in
> the method with static linkage

True.

>> I think that being able to write plugins in C++ is important, and a

> I guess I just don't think that using RTLD_LOCAL is the only reasonable
> way to do it.

The problem is that the use of RTLD_LOCAL is not under the control of the
plugin writer.  And in any case, I think that using RTLD_LOCAL is
appropriate for plugins; we don't want f() in one overriding f() in
another.

Jason

References:
- Re: Duplicate data objects in shared libraries
  - From: Mark Mitchell
- Re: Duplicate data objects in shared libraries
  - From: Jason Merrill
- Re: Duplicate data objects in shared libraries
  - From: Mark Mitchell

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]