[LLVMdev] LLVM 2.9 - JIT problem on Windows

Alan Garny alan.garny at dpag.ox.ac.uk
Fri Nov 25 02:45:09 PST 2011


> > > Now, I may be wrong, but I was under the impression that a call to
> > > InitializeNativeTarget was recommended, if not compulsory, so. why
> > > commenting it out not only makes my LLVM code still work, but also
> > > prevent my application from generating the above error.?!
> >
> > My bet is that your code is writing through a stray pointer. By
> > removing the call to InitializeNativeTarget you are simply hiding your
> > bug by running the code within a context that turns its effects
harmless.
> >
> > OTOH, LLVM 2.9 may be the culprit. In any case, it is time for a
> > assembler- level debug session :-) You can try using the Windows
> > equivalent for valgrind and pray that it catches the problem. Or use
valgrind
> on Linux.
> 
> Thanks, I thought it might be an issue with a stray pointer. It's just
that I
> assumed that since 'my' LLVM code is a shameless copy/paste of one of
> LLVM's examples that it would be fine. Anyway, I am going to investigate
> things further.

Hmm... I have just spent some time going through various Valgrind reports,
but to no avail. Nothing wrong with 'my' LLVM code... Frustrating!

Alan




More information about the llvm-dev mailing list