search for: linkonceodrlinkage

...input. I'm a little confused by the following linkage flags: Enumerator: > > ExternalLinkage: Externally visible function > > AvailableExternallyLinkage: Available for inspection, not emission. > > LinkOnceAnyLinkage: Keep one copy of function when linking (inline) > > LinkOnceODRLinkage: Same, but only replaced by something equivalent. > > WeakAnyLinkage: Keep one copy of named function when linking (weak) > > WeakODRLinkage: Same, but only replaced by something equivalent. > > AppendingLinkage: Special purpose, only applies to global arrays. > > InternalLi...

...structors and destructors lists. We never import these as they would get executed multiple times, which is incorrect. 2.2.4 CommonLinkage Since common symbols are always zero-initialized variables, they do not take up room. It is simplest to import these defs as common. 3 Linkonce Values The LinkOnceODRLinkage and LinkOnceAnyLinkage types refer to linkonce linkage, which allows merging of different globals with the same name. Unreferenced linkonce globals may also be discarded. Linkonce values include some COMDAT functions (COMDAT may also have Weak linkage) and vtable variables. For linkonce values, dup...

...> > For WeakODRLinkage, there is a guarantee that all copies will be > equivalent, so the issue described above for WeakAny does not exist, and > the definition can be imported. For WeakODRLinkage, the imported definition > should retain the original WeakODRLinkage. > > I think LinkOnceODRLinkage has the right semantics here. > > > If imported as a declaration, it should instead have ExternalWeakLinkage. > > I think you can get away with just ExternalLinkage for this? We > found a definition to import, so it must exist somewhere. > > Moreover, thinking about where O...