[llvm-commits] [llvm] r128031 - in /llvm/trunk: include/llvm/ExecutionEngine/RuntimeDyld.h lib/ExecutionEngine/Makefile lib/ExecutionEngine/RuntimeDyld/ lib/ExecutionEngine/RuntimeDyld/CMakeLists.txt lib/ExecutionEngine/RuntimeDyld/Makefile lib/ExecutionEngine/RuntimeDyld/RuntimeDyld.cpp tools/llvm-rtdyld/Makefile tools/llvm-rtdyld/llvm-rtdyld.cpp

[Jan Sjodin]

I was mainly thinking of debug info and being able to run gdb. Would that work?

- Jan




________________________________
From: Jim Grosbach <grosbach at apple.com>
To: Jan Sjodin <jan_sjodin at yahoo.com>
Cc: llvm-commits at cs.uiuc.edu
Sent: Tue, March 22, 2011 4:32:34 PM
Subject: Re: [llvm-commits] [llvm] r128031 - in /llvm/trunk: 
include/llvm/ExecutionEngine/RuntimeDyld.h lib/ExecutionEngine/Makefile 
lib/ExecutionEngine/RuntimeDyld/ lib/ExecutionEngine/RuntimeDyld/CMakeLists.txt 
lib/ExecutionEngine/RuntimeDyld/Makefile 
lib/ExecutionEngine/RuntimeDyld/RuntimeDyld.cpp tools/llvm-rtdyld/Makefile 
tools/llvm-rtdyld/llvm-rtdyld.cpp

That depends on what you're looking to do. What specifically do you mean by 
supporting ELF? The code should work as-is on an ELF based system. It just needs 
the input object file to be a MachO.

Even as this gets fleshed out to handle more things, it's only at the edges 
where the JITed code interfaces with external bits that there's likely to be any 
extra work required to run on an ELF based system, and that should be relatively 
self-contained.

So if you mean whether this infrastructure should work on an ELF based host, 
then yes, at least most of it should work without modification. If you mean 
using ELF as a container instead of MachO, then no, I have no plans to do that.

-Jim
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-commits/attachments/20110322/1f4ab020/attachment.html>