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: gcc visibility used by moz

Gabriel Dos Reis wrote:
Jason Merrill <jason@redhat.com> writes:

So, -concretely- what happens to a class S (e.g. associated type info object
address, address of member functions, etc.) with external linkage,
defined in multiple translation units, with say hidden visibility?

If it has hidden visibility then shared objects other than the one with the definition can't do much with it. They can use inline interfaces and interfaces that are explicitly overridden to have default visibility.

Anything that relies on weak symbols to unify vague linkage entities across shared objects will break. It would be nice to be able to warn about such usage, but I can't think of a way to tell whether we're currently in the defining object or not, and it's not a problem if it's only used within the defining object.

Jason

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