[llvm-commits] [PATCH] Object File Library

[Jason Kim]

I am curious as to  how these patches will impact the existing
MCObjectWriter code. What is the overall intent beyond llvm-nm and
llvm-objdump?

Thanks

-jason

On Sun, Nov 14, 2010 at 5:20 PM, Michael Spencer <bigcheesegs at gmail.com> wrote:
> 2010/11/14 Rafael Espíndola <rafael.espindola at gmail.com>:
>>> I have no problem with that. The only thing I don't like about them
>>> currently is the super typedef macro I had to add to avoid adding 14
>>> lines of typedefs in each templated class :(.
>>
>> Can you declare a base class with just those typedefs? You could then use
>>
>> class foo : public ElfTypeDefs<target_endianness, is64bits>
>
> That's what I originally was trying to do. The problem is that you
> have to explicitly bring the typedefs into scope because of some weird
> C++ template rule.
>
>>> Oh, and I haven't decided how to add writing to
>>> packed_endian_specific_integral yet. Currently it's not possible
>>> (without reinterpret_cast).
>>
>> np. Whatever the solution is (even explicit method calls) is something
>> that can be shared.
>>
>>> - Michael Spencer
>>>
>>
>> Cheers,
>> Rafael
>>
>
> _______________________________________________
> llvm-commits mailing list
> llvm-commits at cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/llvm-commits
>