[llvm-commits] ELFObject

[Danil Malyshev]

Hello,

> 1. Which architecture is to be supported first?

Currently I'm working on the armv7 support.

> 2. How will you split off architecture specific details, such as ..
> 3. Relocations during JIT?

This class provides an access to symbol and relocation data, which is the same for all architectures.
Architecture specific details will be handled by the dynamic linker.

> Is it intended to ever support 64 bit elf files directly? If so, you'll have to do something about the 32bit offset helpers below (for starters) and/or the class name (for clarity) If not, then should this class be called ELF32Object?

I have changed the proposed class to be a template with 2 instances: ELF32Object and ELF64Object.
Please find the patch attached.



Regards,
Danil
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-commits/attachments/20110805/7a076a3a/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ELFObject-02.patch
Type: application/octet-stream
Size: 8828 bytes
Desc: ELFObject-02.patch
URL: <http://lists.llvm.org/pipermail/llvm-commits/attachments/20110805/7a076a3a/attachment.obj>