search for: runconstructor

...} } I then printed the name of the llvm::Function but it was exactly the name I expected "_GLOBAL__sub_I_VectorBIOS.cpp". This code was executed before I added module to the JIT. For various reasons I wanted to store the address to the constructor - so I don't want to call the LLJIT runConstructor - simply because I want to execute those functions later, when the LLJIT does not exist anymore. I hope someone can help me with this... Kind Greetings Björn Als GmbH eingetragen im Handelsregister Bad Homburg v.d.H. HRB 9816, USt.ID-Nr. DE 114 165 789 Geschäftsführer: Dr. Hiroshi Nakamura, Dr. R...

...- Improve JIT support for static initializers: - Add support for running initializers from object files, which will enable loading and caching of objects containing initializers. - Improve support for platform-specific initializer kinds like Objective-C +load methods. - Switch from a push (“runConstructors”) to a pull model (“getConstructorsToRun”) for initializer execution. This will allow JIT’d code to “dlopen” other JIT’d code and run the initializers on the expected thread, which is important for JIT’ing code that uses threads and locks in initializers. - Improve adherence to static/dynamic lin...

Thank you Alex, I went and implemented a solution along those lines. It works well. It may be worth mentioning static constructors in the Kaleidoscope tutorial. Cheers, Daniele ________________________________________ From: Alex Denisov [1101.debian at gmail.com] Sent: 15 March 2019 08:07 To: Daniele Vettorel Cc: llvm-dev at lists.llvm.org Subject: Re: [llvm-dev] Static constructors with ORC