search for: llvminitializer

Hi, Using a JIT engine on LLVM-C currently fails on SVN because the LLVMInitialize???Info is never called. The attached patch fixes this. BTW, would it be possible to include a simple LLVM-C test case, like http://npcontemplation.blogspot.com/2008/06/secret-of-llvm-c-bindings.html, into the test suite, and build/test regularly to prevent regressions like this? Jose -------------- next part

Applied as r79307, thanks On Sat, Aug 15, 2009 at 8:57 AM, José Fonseca<jose.r.fonseca at gmail.com> wrote: > Hi, > > Using a JIT engine on LLVM-C currently fails on SVN because the > LLVMInitialize???Info is never called. > > The attached patch fixes this. > > BTW, would it be possible to include a simple LLVM-C test case, like >

Does the 2.5 release version also fail for this reason? I'm trying to JIT (through LLVM-C) from code generated by my compiler, and it's segfaulting... I'd like to know if this is the problem or if something else is going wrong. On Mon, Aug 17, 2009 at 10:06 PM, Daniel Dunbar<daniel at zuster.org> wrote: > Applied as r79307, thanks > > On Sat, Aug 15, 2009 at 8:57 AM,

I actually had an idea about how to fix this in a relatively painless manner. Although given my experience over the past 4 days, it might not be best to call it painless without first trying :) The idea is to make a StaticPassRegistry. RegisterPass<> only touches the StaticPassRegistry, and nothing else touches the StaticPassRegistry. So once you enter main(), StaticPassRegistry can be

The mutex could be made an actual global static instead of a ManagedStatic. This guarantees it would be constructed before main, and live until the end of main. So even in PassRegistry's destructor, which would get call during llvm_shutdown(), it would always have the same mutex. Ideally I'd like to just delete the mutex, as it doesn't seem like anyone is using it in a

Hola Aaron, Just having that code didn't work since the linker still stripped it out, so I have that function called from the code in the system that actually is being used by our app. Kinda grubby, but I include: #include "llvm/lib/Target/X86/X86TargetMachine.h" Which is in the LLVM lib, not the LLVM inc directory. This little maneuver made our Mac builds really unhappy, so

Thanks for your response Chuck. >From this and the other responses to my question, it looks like I'm including all the right object files, so it must be something with Visual Studio stripping "dead" code. So, given your response Chuck, I have a few questions. First, what exactly is the code that VStudio seems to be stripping? I might be able to figure out how to prevent it

+cc original authors of these changes. Is PassRegistry intended to be thread-safe? The header file explicitly says that PassRegistry is not thread-safe, but there are mutexes and locking used in the code. This is actually creating a problem, because of a subtle bug involving static initialization order and shutdown. In particular, the RegisterPass<> static template will get invoked