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

[Borja F. <bor...@gm...>]

Ahh i see, that's fine.
I've just commited a patch file that adds some custom code to the register
allocator that reserves REG_Y on the fly when it's used as a frame pointer.
This has given me a bit of a headache because with the current API it's not
possible to do it, so I had to add a small hack to make it work, now it's
behaving the same way as GCC.
Next I have to work at passing local stack variables as parameters to
functions and allocating stack space, I think that should be it related to
stack and frame work (I'm leaving varargs for later xD).

2011/11/21 Anton Staaf <an...@so...>

> Hi Borja, I haven't done anything much.  I have been lurking on the
> Clang and LLVM lists as well gaining insight and poking at code.  It
> looks like there is a renewed effort in the abstraction of calling
> convention and architecture independence from developers on both sides
> of the bitcode divide.  Which would be great for backends like this
> one.
>
> But I've spent most of my open source programming time on U-Boot
> actually.  I am very interested in your new AVR backend and would love
> to play with it and help out.  I look forward to seeing it.  :)
>
> Thanks,
>     Anton
>
> On Wed, Oct 12, 2011 at 4:19 PM, Borja Ferrer <bor...@gm...>
> wrote:
> > Hello everybody, I'm sorry about the long time without any updates
> (around
> > june), I've been very busy during these months so I've been unable to do
> any
> > work. Did anybody advanced on something during this time?
> > If i remember correctly the last thing i was working on were stack
> frames,
> > so i'll continue the work from there. But first I'll have to update
> myself
> > to see the changes in llvm's trunk during all this time, and then update
> my
> > local repo to compile with their latest code, I'm guessing some work
> there
> > because of their API changes. This will take me some days, and then back
> to
> > coding.
> >
> > 2011/6/23 Anton Staaf <an...@so...>
> >>>
> >>> Your patches are on the right track, however please dont spend much
> time
> >>> taking a look and working with the current backend in SVN because it's
> going
> >>> to be completely replaced. I would recommend taking a read through
> previous
> >>> threads in the mailing list to take a grasp of what is the current
> status
> >>> and what are the problems we've been having and how some have been
> resolved,
> >>> I would say bacl from October-2010 to today. Many interface changes are
> >>> happening in LLVM so I doubt the backend compiles at all for the latest
> >>> release.
> >>
> >> Yup, that's what I had gathered.  I am very much looking forward to the
> >> new back-end going up.  I'd love to help out with it.
> >>>
> >>> As a short summary, I have a more developed backend out of SVN with a
> >>> completely different design (you can read about it in older threads)
> that
> >>> has to be uploaded. Currently, I'm working on everything related to
> frame
> >>> stuff which is a big milestone. I have to ask something to the llvm
> devs
> >>> because I'm stuck on something before continuing the work.
> >>
> >> Indeed, I was tracking your conversation about function preambles.  It
> >> seems like while supporting both the IAR and GCC styles would be very
> useful
> >> (perhaps with IAR behind a flag) it would also be considerable work.
>  Have
> >> you decided on a stack management style?
> >>>
> >>> You mentioned about helping on the Clang side, that would be awesome
> >>> because right now nobody is working on that, and indeed, all the
> address
> >>> space stuff has to be resolved, so your work there would be really
> >>> appreciated.
> >>
> >> Good to hear, I've been continuing to experiment there.
> >>>
> >>> PS: since mid may I'm inactive because of my finals until july so i
> wont
> >>> be able to resume work until then, but i'll keep reading the mailing
> list to
> >>> follow up any discussions.
> >>
> >> Good luck on your finals.
> >> Thanks,
> >>     Anton
> >
> >
>