[LLVMbugs] [Bug 15729] New: RuntimeDyld doesn't handle calls to external functions from MachO objects

[bugzilla-daemon at llvm.org]

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

            Bug ID: 15729
           Summary: RuntimeDyld doesn't handle calls to external functions
                    from MachO objects
           Product: libraries
           Version: trunk
          Hardware: All
                OS: All
            Status: NEW
          Severity: normal
          Priority: P
         Component: Generic Execution Engine Support
          Assignee: unassignedbugs at nondot.org
          Reporter: andrew.kaylor at intel.com
                CC: llvmbugs at cs.uiuc.edu
    Classification: Unclassified

Created attachment 10343
  --> http://llvm.org/bugs/attachment.cgi?id=10343&action=edit
sample code to reproduce the problem

RuntimeDyld fails with an assertion when trying to perform relocations on
generated code that contains a call to an external function.  The generated
code contains a relocation (which varies by architecture) that is not handled
by the RuntimeDyldMachO class.

Eran Weiss provided the attached sample code to reproduce the problem.

To reproduce:

$ /usr/bin/g++ `llvm-config --cxxflags` -g -m32 -c mcjit_external_symbol.cpp
$ /usr/bin/g++ `llvm-config --ldflags` -g -m32 -o mcjit_external_symbol
mcjit_external_symbol.o `llvm-config --libs all`
$ ./mcjit_external_symbol 
verifying... 
LLVM ERROR: Program used external function '_external' which could not be
resolved!


This same test case passes if the older JIT implementation is used.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-bugs/attachments/20130411/9d062a1a/attachment.html>