[LLVMbugs] [Bug 2606] New: global variables declared in module A but defined in module B are not resolved by the JIT

[bugzilla-daemon at cs.uiuc.edu]

http://llvm.org/bugs/show_bug.cgi?id=2606

           Summary: global variables declared in module A but defined in
                    module B are not resolved by the JIT
           Product: libraries
           Version: trunk
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Generic Execution Engine Support
        AssignedTo: unassignedbugs at nondot.org
        ReportedBy: paul at rapidmind.com
                CC: llvmbugs at cs.uiuc.edu


Created an attachment (id=1868)
 --> (http://llvm.org/bugs/attachment.cgi?id=1868)
modified HowToUseJIT.cpp which reproduces the problem

If you declare and use a global variable in module A and define it in module B
the execution engine will not resolve the symbol in module A.

The attached modified version of HowToUseJIT.cpp shows this problem. You can
manually work around this limitation by explicitly calling addGlobalMapping on
the declaration using the same pointer that's mapped to the definition.


-- 
Configure bugmail: http://llvm.org/bugs/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.