Re: [avr-llvm-devel] Just getting started, but eager to help (subscribed to the list this time...)

[Anton S. <an...@so...>]

John,

On Fri, Jun 10, 2011 at 11:41 AM, John Myers <ato...@gm...>wrote:

> Hi Anton,
>
>
> On Thu, Jun 9, 2011 at 9:41 PM, Anton Staaf <an...@so...>wrote:
>
>>     Hello Borja, John, Eric and all,
>>
> I would love to see great Clang/LLVM support for the AVR architecture.  And
>> so I'm hoping to help out here.
>>
> Do you have a sourceforge account?
>

I do, I'm not sure I understand the connection though.  :)

    The two issues I ran into are that TargetMachine::getFrameInfo() has
>> been renamed to TargetMachine::getFrameLowering() and that
>> TargetLowering::ReplaceNodeResults was not implemented in AVRTargetLowering.
>>  I don't expect that the patches below will be very useful by them selves.
>>  I'm more curious if I'm at least on the right page.
>>
>> Which svn version are you using? Some of the changes in your patches are
> already committed (rev 110). You're on the right page but wrong sentence :)
> There is a lot of refactoring of clang/LLVM like this which sometimes makes
> it hard to keep up with ToT of clang/LLVM. For me at least it's been a good
> way of becoming a little more familiar with the internals of LLVM.
>

I based my patch against revision 121.  I'll take a look and see what
happened, but at least I know I wasn't in the weeds.


>
>>     It seems like until the new backend is available it may be more worth
>> my time looking into helping out with the Clang cross compilation work.  In
>> particular the TargetInfo being baked into libs/Basic/Targets.cpp seems like
>> an area for cleanup.  I think that there was a thread about this on the
>> clang list recently.  I'll do some more reading there.
>>
>>     Thanks,
>>         Anton
>>
>
> Yeah, I agree. I've been spending my time trying to get familiar with clang
> and how the toolchain/driver code works.
>
>
> --John
>