search for: globalctor

...ote: > > >> Dear All, >> >> Are global static constructors called before main() in LLVM these days >> using some behind-the-scenes magic that is not explicit in the LLVM >> bitcode? >> > > It is explicit in the bitcode. You should see an llvm.globalctors > global array that has function pointers for each initializer to run. > Right, I saw that. I just didn't see anything from main() calling those functions, which led me to believe that something else is calling those functions before main(). >> In older versions of LLVM,...

Dear All, Are global static constructors called before main() in LLVM these days using some behind-the-scenes magic that is not explicit in the LLVM bitcode? In older versions of LLVM, llvm-gcc added an explicit function call to __main() as the first instruction in main(); __main() would call all global static constructors. It seems __main() is now gone. I've got a transform that

On Dec 11, 2008, at 2:35 PM, John Criswell wrote: > Dear All, > > Are global static constructors called before main() in LLVM these days > using some behind-the-scenes magic that is not explicit in the LLVM > bitcode? It is explicit in the bitcode. You should see an llvm.globalctors global array that has function pointers for each initializer to run. > In older versions of LLVM, llvm-gcc added an explicit function > call to __main() as the first instruction in main(); __main() would > call > all global static constructors. It seems __main() is now gone. Ye...

On Dec 11, 2008, at 2:45 PM, John Criswell wrote: >> It is explicit in the bitcode. You should see an llvm.globalctors >> global array that has function pointers for each initializer to run. >> > Right, I saw that. I just didn't see anything from main() calling > those > functions, which led me to believe that something else is calling > those > functions before main(). Yep, th...

...p://llvm.cs.uiuc.edu/docs/BytecodeFormat.html#globalinfo > Did you think about a mapping of common attributes on different > platforms. For instance DLLMain Entry point under Win32 and the > __attribute__((constructor)) under Linux. __attribute__((constructor)) is handled with a the llvm.globalctors global variable (even with llvm 1.6), try it out. >>> I would generally be interested and could contribute to extending LLVM >>> by allowing more Annotatinons than currently possible. > Okay so I am on quite the opposite attitude than the LLVM team towards > that issue :...

hi Chris! thanks for your reply. First of all I did not know about the history with the Annotation stuff. Annotable for me was a way how one could realize this things. So as I see it right now - it is more that Annotable will completly vanish soon. This is interesting to me. Chris Lattner schrieb: > On Fri, 24 Feb 2006, Jakob Praher wrote: > >> When translating a complex c