search for: _global_i_a

...tions reused for two globals in the same TU? Even today, every global with a dynamic initializer gets its own void() initialization function. We don't use a single function to initialize everything. We need to enforce an ordering on initializers in a single TU, so we have a function (usually _GLOBAL_I_a) which calls each stub in turn. After inlining, most stubs are probably eliminated. > Thanks, Duncan. > > Similarly, on > >> targets supporting this feature (COFF for the moment, but maybe ELF one >> day as >> an optimization), LLVM will emit the appropriate comdat...

Hi Reid, On 26/08/13 23:43, Reid Kleckner wrote: > To implement http://llvm.org/PR16959 > <http://llvm.org/bugs/show_bug.cgi?id=16959>, I need to add a new field to > global_ctors. > > Static data members of class template instantiations can have initializers that > must only run once on program startup. Itanium solves this with guard variables > and the emission of

...field meaning: collapse multiple instances of this initialization function. In fact, maybe it is always OK to remove duplicate initialization functions in llvm.global_ctors? Ciao, Duncan. > > We need to enforce an ordering on initializers in a single TU, so we have a > function (usually _GLOBAL_I_a) which calls each stub in turn. After inlining, > most stubs are probably eliminated. > > Thanks, Duncan. > > Similarly, on > > targets supporting this feature (COFF for the moment, but maybe ELF one > day as > an optimization), LLVM wil...

To implement http://llvm.org/PR16959<http://llvm.org/bugs/show_bug.cgi?id=16959>, I need to add a new field to global_ctors. Static data members of class template instantiations can have initializers that must only run once on program startup. Itanium solves this with guard variables and the emission of multiple initializers, only one of which actually initializes the data at runtime.