Re: [avr-llvm-devel] Fwd: Sync with trunk

[John M. <ato...@gm...>]

Like Stepan has said, maintaining the patches with SVN on an out-of-tree
project often causes issues.
If we just had one big monolithic patch then it wouldn't be an issue.
I suspect doing major work on parts of LLVM outside of *lib/target/AVR *will
also cause similar maintainability issues uses SVN.


On Mon, Jun 10, 2013 at 10:46 AM, Stepan Dyatkovskiy <stp...@na...>wrote:

> Hi Borja,
> I think John means all this stuff with .diff files that lies under svn.
>
> I've tried several mid-January revisions with r247. But I couldn't get
> compilable version. Would you tell me please what "svn info" says in
> your llvm project?
>
> All AVR tests has been failed after my own sync (r244). Seems I've
> missed something.
>
> -Stepan.
>
> Borja Ferrer wrote:
> > Eric, what do you exactly mean? Trunk changes in LLVM are automatically
> > merged in your local repo when you update, and when we need to update
> > our code base to fix interface changes we have to do it manually but
> > that's the only way I know of.
> >
> > Stepan: the old sourceforge repo
> > (http://avr-llvm.svn.sourceforge.net/viewvc/avr-llvm/) should work with
> > the LLVM trunk version of that time (mid january). I have to update our
> > code to latest LLVM trunk so we can compile the backend with their
> > newest code. What tests are failing for you? IIRC i only got failures
> > with tests not related with our backend. And another thing, are you
> > working on adding inline asm support?
> >
> >
> > 2013/6/10 Stepan Dyatkovskiy <stp...@na... <mailto:
> stp...@na...>>
> >
> >     Guys, my sync + r244 gave me AVR test failures. Do you have
> >     somewhere repo with actual things (even with old llvm) ?
> >     -Stepan
> >
> >     Borja Ferrer wrote:
> >
> >         Wow the SF migration has messed my last 5 commits, John I just
> >         noticed
> >         that you merged some of them into the new repo but some are
> >         still missing.
> >
> >         Regarding the status since it has been asked, the most important
> >         thing
> >         to be done in the backend side is inline asm support, as John
> >         mentioned
> >         the backend should be able to compile now any feature except for
> >         this.
> >         The frontend needs some more work, basically getting a working
> >         toolchain
> >         done.
> >
> >         About the version control in atmel spaces, I'm only familiar
> >         with CVS
> >         and SVN, never worked before with git and mercurial.
> >
> >
> >
> ------------------------------__------------------------------__------------------
> >         How ServiceNow helps IT people transform IT departments:
> >         1. A cloud service to automate IT design, transition and
> operations
> >         2. Dashboards that offer high-level views of enterprise services
> >         3. A single system of record for all IT processes
> >         http://p.sf.net/sfu/__servicenow-d2d-j
> >         <http://p.sf.net/sfu/servicenow-d2d-j>
> >
> >
> >
> >         _________________________________________________
> >         avr-llvm-devel mailing list
> >         avr-llvm-devel@lists.__sourceforge.net
> >         <mailto:avr...@li...>
> >         https://lists.sourceforge.net/__lists/listinfo/avr-llvm-devel
> >         <https://lists.sourceforge.net/lists/listinfo/avr-llvm-devel>
> >
> >
> >
>
>
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by Windows:
>
> Build for Windows Store.
>
> http://p.sf.net/sfu/windows-dev2dev
> _______________________________________________
> avr-llvm-devel mailing list
> avr...@li...
> https://lists.sourceforge.net/lists/listinfo/avr-llvm-devel
>