[LLVMdev] LLVM 3.0 - Windows - auto-importing issue with llvm::CallInst

Alan Garny alan.garny at dpag.ox.ac.uk
Fri Dec 2 07:09:45 PST 2011



I have just upgraded to LLVM 3.0 (nice job btw!) which I have built as a
shared library on Windows using MinGW, and then use from within my Qt-based
application. Upon execution, everything works perfectly (incl. the call to
llvm::InitializeNativeTarget(); which used to cause problems upon exiting my
application; see
http://lists.cs.uiuc.edu/pipermail/llvmdev/2011-November/045597.html; in
other words, there is something wrong in LLVM 2.9, but that somehow got
fixed in LLVM 3.0).


However, there is one new (minor) issue which is that when building my
application I get a warning from the linker about auto-importing having been
activated without -enable-auto-import being specified on the command line.
Indeed, for some reason, the vtable for llvm::CallInst has to be resolved.?!
This is clearly not critical since I can get rid of the warning by adding
-enable-auto-import on the command line, but I wish I didn't have to do that
(it's not clean in my view).


So. how come I am getting that warning and how could I get rid of it without
having to rely on the -enable-auto-import argument?


Cheers, Alan.


PS: everything works is fine on Linux x86/x64 and Mac OS X. Brilliant! J

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20111202/9bcefff6/attachment.html>

More information about the llvm-dev mailing list