Menu
▾
▴
avr-llvm-devel
|
From: Borja F. <bor...@gm...> - 2013-06-10 11:48:26
|
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. |
|
From: Weddington, E. <Eri...@at...> - 2013-06-10 16:16:58
|
> -----Original Message----- > From: Borja Ferrer [mailto:bor...@gm...] > Sent: Monday, June 10, 2013 5:48 AM > To: avr...@li... > Subject: [avr-llvm-devel] Fwd: Sync with trunk > > About the version control in atmel spaces, I'm only familiar with CVS > and SVN, never worked before with git and mercurial. Is it easy enough to sync with LLVM using SVN? |
|
From: Stepan D. <stp...@na...> - 2013-06-10 17:15:24
|
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 > > > > _______________________________________________ > avr-llvm-devel mailing list > avr...@li... > https://lists.sourceforge.net/lists/listinfo/avr-llvm-devel > |
|
From: Borja F. <bor...@gm...> - 2013-06-10 17:33:19
|
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...> > 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<avr...@li...> >> https://lists.sourceforge.net/**lists/listinfo/avr-llvm-devel<https://lists.sourceforge.net/lists/listinfo/avr-llvm-devel> >> >> > |
|
From: Weddington, E. <Eri...@at...> - 2013-06-10 17:36:26
|
> -----Original Message----- > From: Borja Ferrer [mailto:bor...@gm...] > Sent: Monday, June 10, 2013 11:33 AM > To: Stepan Dyatkovskiy; Weddington, Eric > Cc: avr...@li... > Subject: Re: [avr-llvm-devel] Fwd: Sync with trunk > > 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. All I'm trying to figure out is what would be the best VCS for us to use (svn or git) in moving over to Atmel Spaces. If using one over the other makes it easier to do some tasks (like staying in sync with llvm trunk), then we should go with the one that makes it easier. If it doesn't really matter, then I suggest just sticking with svn. Eric |
|
From: Borja F. <bor...@gm...> - 2013-06-10 17:45:33
|
Ok then, guys that have used GIT before please discuss any advantages here. As i said, i havent used GIT before so i can't add any valuable points. I've been able to work with SVN and LLVM quite well so far though. 2013/6/10 Weddington, Eric <Eri...@at...> > > > > -----Original Message----- > > From: Borja Ferrer [mailto:bor...@gm...] > > Sent: Monday, June 10, 2013 11:33 AM > > To: Stepan Dyatkovskiy; Weddington, Eric > > Cc: avr...@li... > > Subject: Re: [avr-llvm-devel] Fwd: Sync with trunk > > > > 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. > > All I'm trying to figure out is what would be the best VCS for us to use > (svn or git) in moving over to Atmel Spaces. If using one over the other > makes it easier to do some tasks (like staying in sync with llvm trunk), > then we should go with the one that makes it easier. > > If it doesn't really matter, then I suggest just sticking with svn. > > Eric > |
|
From: Stepan D. <stp...@na...> - 2013-06-10 18:06:10
|
Hello Borja, Git allows you to clone LLVM project (it has GIT mirror), and develop your backend in your own branch. You will *never* lose commits under git, since it is distributed VCS and everyone keeps clone of all project history. There is good one-day git tutorial: http://git-scm.com/documentation -Stepan. Borja Ferrer wrote: > Ok then, guys that have used GIT before please discuss any advantages > here. As i said, i havent used GIT before so i can't add any valuable > points. I've been able to work with SVN and LLVM quite well so far though. > > > 2013/6/10 Weddington, Eric <Eri...@at... > <mailto:Eri...@at...>> > > > > > -----Original Message----- > > From: Borja Ferrer [mailto:bor...@gm... > <mailto:bor...@gm...>] > > Sent: Monday, June 10, 2013 11:33 AM > > To: Stepan Dyatkovskiy; Weddington, Eric > > Cc: avr...@li... > <mailto:avr...@li...> > > Subject: Re: [avr-llvm-devel] Fwd: Sync with trunk > > > > 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. > > All I'm trying to figure out is what would be the best VCS for us to > use (svn or git) in moving over to Atmel Spaces. If using one over > the other makes it easier to do some tasks (like staying in sync > with llvm trunk), then we should go with the one that makes it easier. > > If it doesn't really matter, then I suggest just sticking with svn. > > Eric > > |
|
From: Stepan D. <stp...@na...> - 2013-06-10 17:46:47
|
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> > > > |
|
From: John M. <ato...@gm...> - 2013-06-10 18:27:39
|
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 > |
|
From: John M. <ato...@gm...> - 2013-06-10 17:49:24
|
Borja, I still need to update the new repo with two more of your commits. On Mon, Jun 10, 2013 at 4:48 AM, Borja Ferrer <bor...@gm...> 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 > _______________________________________________ > avr-llvm-devel mailing list > avr...@li... > https://lists.sourceforge.net/lists/listinfo/avr-llvm-devel > > |
|
From: Borja F. <bor...@gm...> - 2013-06-10 17:59:10
|
Great, thanks John. Stepan, here it is: LLVM SVN info: Revisión: 172075 Autor del último cambio: tnorthover Fecha de último cambio: 2013-01-10 16:17:36 +0100 (jue 10 de ene de 2013) AVR-LLVM SVN info: Ruta: . Revisión: 247 Autor del último cambio: faluco Fecha de último cambio: 2013-01-12 00:36:55 +0100 (sáb 12 de ene de 2013) 2013/6/10 John Myers <ato...@gm...> > Borja, I still need to update the new repo with two more of your commits. > > > On Mon, Jun 10, 2013 at 4:48 AM, Borja Ferrer <bor...@gm...>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 >> _______________________________________________ >> avr-llvm-devel mailing list >> avr...@li... >> https://lists.sourceforge.net/lists/listinfo/avr-llvm-devel >> >> > |
|
From: Borja F. <bor...@gm...> - 2013-06-10 18:01:28
|
Thanks for the link Stepan, I'll take a look. 2013/6/10 Stepan Dyatkovskiy <stp...@na...> > Hello Borja, > Git allows you to clone LLVM project (it has GIT mirror), and develop your > backend in your own branch. You will *never* lose commits under git, since > it is distributed VCS and everyone keeps clone of all project history. > There is good one-day git tutorial: > http://git-scm.com/**documentation <http://git-scm.com/documentation> > > -Stepan. > > Borja Ferrer wrote: > >> Ok then, guys that have used GIT before please discuss any advantages >> here. As i said, i havent used GIT before so i can't add any valuable >> points. I've been able to work with SVN and LLVM quite well so far though. >> >> >> 2013/6/10 Weddington, Eric <Eri...@at... >> <mailto:Eric.Weddington@atmel.**com <Eri...@at...>>> >> >> >> >> >> > -----Original Message----- >> > From: Borja Ferrer [mailto:bor...@gm... >> <mailto:bor...@gm...>**] >> > Sent: Monday, June 10, 2013 11:33 AM >> > To: Stepan Dyatkovskiy; Weddington, Eric >> > Cc: avr-llvm-devel@lists.**sourceforge.net<avr...@li...> >> <mailto:avr-llvm-devel@lists.**sourceforge.net<avr...@li...> >> > >> > Subject: Re: [avr-llvm-devel] Fwd: Sync with trunk >> > >> > 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. >> >> All I'm trying to figure out is what would be the best VCS for us to >> use (svn or git) in moving over to Atmel Spaces. If using one over >> the other makes it easier to do some tasks (like staying in sync >> with llvm trunk), then we should go with the one that makes it easier. >> >> If it doesn't really matter, then I suggest just sticking with svn. >> >> Eric >> >> >> > |
|
From: Stepan D. <stp...@na...> - 2013-06-10 18:07:00
|
And you thanks :-) Will compile it again. Today I did some survey how InlineAsm class is working, how it expanded in back-end. Though I couldn't start to implement it in AVR. So, I hope will start to do it today :-) -Stepan. Borja Ferrer wrote: > Thanks for the link Stepan, I'll take a look. > > > 2013/6/10 Stepan Dyatkovskiy <stp...@na... <mailto:stp...@na...>> > > Hello Borja, > Git allows you to clone LLVM project (it has GIT mirror), and > develop your backend in your own branch. You will *never* lose > commits under git, since it is distributed VCS and everyone keeps > clone of all project history. > There is good one-day git tutorial: > http://git-scm.com/__documentation <http://git-scm.com/documentation> > > -Stepan. > > Borja Ferrer wrote: > > Ok then, guys that have used GIT before please discuss any > advantages > here. As i said, i havent used GIT before so i can't add any > valuable > points. I've been able to work with SVN and LLVM quite well so > far though. > > > 2013/6/10 Weddington, Eric <Eri...@at... > <mailto:Eri...@at...> > <mailto:Eric.Weddington@atmel.__com > <mailto:Eri...@at...>>> > > > > > > -----Original Message----- > > From: Borja Ferrer [mailto:bor...@gm... > <mailto:bor...@gm...> > <mailto:bor...@gm... > <mailto:bor...@gm...>>__] > > Sent: Monday, June 10, 2013 11:33 AM > > To: Stepan Dyatkovskiy; Weddington, Eric > > Cc: avr-llvm-devel@lists.__sourceforge.net > <mailto:avr...@li...> > <mailto:avr-llvm-devel@lists.__sourceforge.net > <mailto:avr...@li...>> > > Subject: Re: [avr-llvm-devel] Fwd: Sync with trunk > > > > 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. > > All I'm trying to figure out is what would be the best VCS > for us to > use (svn or git) in moving over to Atmel Spaces. If using > one over > the other makes it easier to do some tasks (like staying in > sync > with llvm trunk), then we should go with the one that makes > it easier. > > If it doesn't really matter, then I suggest just sticking > with svn. > > Eric > > > > |
|
From: Stepan D. <stp...@na...> - 2013-06-10 18:33:57
|
Gotcha :-) All tests has been passed :-) -Stepan. Stepan Dyatkovskiy wrote: > And you thanks :-) > Will compile it again. Today I did some survey how InlineAsm class is > working, how it expanded in back-end. Though I couldn't start to > implement it in AVR. So, I hope will start to do it today :-) > > -Stepan. > Borja Ferrer wrote: >> Thanks for the link Stepan, I'll take a look. >> >> >> 2013/6/10 Stepan Dyatkovskiy <stp...@na... <mailto:stp...@na...>> >> >> Hello Borja, >> Git allows you to clone LLVM project (it has GIT mirror), and >> develop your backend in your own branch. You will *never* lose >> commits under git, since it is distributed VCS and everyone keeps >> clone of all project history. >> There is good one-day git tutorial: >> http://git-scm.com/__documentation <http://git-scm.com/documentation> >> >> -Stepan. >> >> Borja Ferrer wrote: >> >> Ok then, guys that have used GIT before please discuss any >> advantages >> here. As i said, i havent used GIT before so i can't add any >> valuable >> points. I've been able to work with SVN and LLVM quite well so >> far though. >> >> >> 2013/6/10 Weddington, Eric <Eri...@at... >> <mailto:Eri...@at...> >> <mailto:Eric.Weddington@atmel.__com >> <mailto:Eri...@at...>>> >> >> >> >> >> > -----Original Message----- >> > From: Borja Ferrer [mailto:bor...@gm... >> <mailto:bor...@gm...> >> <mailto:bor...@gm... >> <mailto:bor...@gm...>>__] >> > Sent: Monday, June 10, 2013 11:33 AM >> > To: Stepan Dyatkovskiy; Weddington, Eric >> > Cc: avr-llvm-devel@lists.__sourceforge.net >> <mailto:avr...@li...> >> <mailto:avr-llvm-devel@lists.__sourceforge.net >> <mailto:avr...@li...>> >> > Subject: Re: [avr-llvm-devel] Fwd: Sync with trunk >> > >> > 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. >> >> All I'm trying to figure out is what would be the best VCS >> for us to >> use (svn or git) in moving over to Atmel Spaces. If using >> one over >> the other makes it easier to do some tasks (like staying in >> sync >> with llvm trunk), then we should go with the one that makes >> it easier. >> >> If it doesn't really matter, then I suggest just sticking >> with svn. >> >> Eric >> >> >> >> > > > ------------------------------------------------------------------------------ > 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 > |
|
From: Borja F. <bor...@gm...> - 2013-06-10 19:14:25
|
Great Stepan! Yes John, patches are a real pain, my question is: would git simplify managing them compared to svn? 2013/6/10 Stepan Dyatkovskiy <stp...@na...> > Gotcha :-) All tests has been passed :-) > -Stepan. > > Stepan Dyatkovskiy wrote: > >> And you thanks :-) >> Will compile it again. Today I did some survey how InlineAsm class is >> working, how it expanded in back-end. Though I couldn't start to >> implement it in AVR. So, I hope will start to do it today :-) >> >> -Stepan. >> Borja Ferrer wrote: >> >>> Thanks for the link Stepan, I'll take a look. >>> >>> >>> 2013/6/10 Stepan Dyatkovskiy <stp...@na... <mailto: >>> stp...@na...>> >>> >>> Hello Borja, >>> Git allows you to clone LLVM project (it has GIT mirror), and >>> develop your backend in your own branch. You will *never* lose >>> commits under git, since it is distributed VCS and everyone keeps >>> clone of all project history. >>> There is good one-day git tutorial: >>> http://git-scm.com/__**documentation<http://git-scm.com/__documentation>< >>> http://git-scm.com/**documentation <http://git-scm.com/documentation>> >>> >>> -Stepan. >>> >>> Borja Ferrer wrote: >>> >>> Ok then, guys that have used GIT before please discuss any >>> advantages >>> here. As i said, i havent used GIT before so i can't add any >>> valuable >>> points. I've been able to work with SVN and LLVM quite well so >>> far though. >>> >>> >>> 2013/6/10 Weddington, Eric <Eri...@at... >>> <mailto:Eric.Weddington@atmel.**com <Eri...@at...> >>> > >>> <mailto:Eric.Weddington@atmel.**__com >>> <mailto:Eric.Weddington@atmel.**com <Eri...@at...> >>> >>> >>> >>> >>> >>> >>> > -----Original Message----- >>> > From: Borja Ferrer [mailto:bor...@gm... >>> <mailto:bor...@gm...> >>> <mailto:bor...@gm... >>> <mailto:bor...@gm...>**>__] >>> > Sent: Monday, June 10, 2013 11:33 AM >>> > To: Stepan Dyatkovskiy; Weddington, Eric >>> > Cc: avr-llvm-devel@lists.__sourcef**orge.net<http://sourceforge.net> >>> <mailto:avr-llvm-devel@lists.**sourceforge.net<avr...@li...> >>> > >>> <mailto:avr-llvm-devel@lists._**_sourceforge.net >>> <mailto:avr-llvm-devel@lists.**sourceforge.net<avr...@li...> >>> >> >>> > Subject: Re: [avr-llvm-devel] Fwd: Sync with trunk >>> > >>> > 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. >>> >>> All I'm trying to figure out is what would be the best VCS >>> for us to >>> use (svn or git) in moving over to Atmel Spaces. If using >>> one over >>> the other makes it easier to do some tasks (like staying in >>> sync >>> with llvm trunk), then we should go with the one that makes >>> it easier. >>> >>> If it doesn't really matter, then I suggest just sticking >>> with svn. >>> >>> Eric >>> >>> >>> >>> >>> >> >> ------------------------------**------------------------------** >> ------------------ >> This SF.net email is sponsored by Windows: >> >> Build for Windows Store. >> >> http://p.sf.net/sfu/windows-**dev2dev<http://p.sf.net/sfu/windows-dev2dev> >> ______________________________**_________________ >> avr-llvm-devel mailing list >> avr-llvm-devel@lists.**sourceforge.net<avr...@li...> >> https://lists.sourceforge.net/**lists/listinfo/avr-llvm-devel<https://lists.sourceforge.net/lists/listinfo/avr-llvm-devel> >> >> > |
|
From: Stepan D. <stp...@na...> - 2013-06-11 16:03:35
|
Hello John,
As I mentioned before, my sync was not very successful. *All* AVR tests
had been crashed.
So, currently I'm working with what-you-have code: r172075(LLVM) + r247
(avr-llvm).
I've implemented very draft version of inline assembly. If you still
want to use SVN I'll create you .diff tomorrow then. Though you can get
it today via GIT.
Today I did two things:
1. Implemented very draft inline assembler support.
2. Ported your svn repo (with whole history) to git and published it on
github (though, you can move it to any place):
2.1. Initially I've just cloned everything from svn to git. I got the
whole your history with the only branch. SVN branches are just a subfolders.
2.2. I've moved AVR folder to repo's root. And removed cfe and dragonegg
code (it should be tracked with another repo).
2.3. I've cloned llvm.git, checked out r172075, and attached our project
as lib/Target/AVR sub-folder.
Finally I got two branches of code:
>--- llvm commits are ---------------->[r172075]-----llvm-commits---->
\
- avr branch --->
/
>-- avr llvm commits --------[r247]
Currently I've published it on github. But, of course, you can clone it
and move to any place you want.
This command:
"git clone -b avr git://github.com/kaomoneus/avr-llvm.git"
clones all the llvm code, with AVR target inside (with draft inline asm
support ;-) ).
Currently it is merged only with r172075. I'll try to merge it with llvm
ToT tomorrow.
I'll online till 13:00 UTC-7, so any questions are welcome.
-Stepan.
John Myers wrote:
> Hi Stepan,
>
> Can you make a new unified diff based on the current repo?
> I'm still not able to get some of your patches to apply cleanly.
>
> P.S.
> I can give you write access to the repo if you want. Just let me know
> your sourceforge username.
>
>
> On Mon, Jun 10, 2013 at 11:33 AM, Stepan Dyatkovskiy <stp...@na...
> <mailto:stp...@na...>> wrote:
>
> Gotcha :-) All tests has been passed :-)
> -Stepan.
>
> Stepan Dyatkovskiy wrote:
> > And you thanks :-)
> > Will compile it again. Today I did some survey how InlineAsm class is
> > working, how it expanded in back-end. Though I couldn't start to
> > implement it in AVR. So, I hope will start to do it today :-)
> >
> > -Stepan.
> > Borja Ferrer wrote:
> >> Thanks for the link Stepan, I'll take a look.
> >>
> >>
> >> 2013/6/10 Stepan Dyatkovskiy <stp...@na...
> <mailto:stp...@na...> <mailto:stp...@na...
> <mailto:stp...@na...>>>
> >>
> >> Hello Borja,
> >> Git allows you to clone LLVM project (it has GIT mirror), and
> >> develop your backend in your own branch. You will *never* lose
> >> commits under git, since it is distributed VCS and everyone
> keeps
> >> clone of all project history.
> >> There is good one-day git tutorial:
> >> http://git-scm.com/__documentation
> <http://git-scm.com/documentation>
> >>
> >> -Stepan.
> >>
> >> Borja Ferrer wrote:
> >>
> >> Ok then, guys that have used GIT before please discuss any
> >> advantages
> >> here. As i said, i havent used GIT before so i can't
> add any
> >> valuable
> >> points. I've been able to work with SVN and LLVM quite
> well so
> >> far though.
> >>
> >>
> >> 2013/6/10 Weddington, Eric <Eri...@at...
> <mailto:Eri...@at...>
> >> <mailto:Eri...@at...
> <mailto:Eri...@at...>>
> >> <mailto:Eric.Weddington@atmel.
> <mailto:Eric.Weddington@atmel.>__com
> >> <mailto:Eri...@at...
> <mailto:Eri...@at...>>>>
> >>
> >>
> >>
> >>
> >> > -----Original Message-----
> >> > From: Borja Ferrer
> [mailto:bor...@gm... <mailto:bor...@gm...>
> >> <mailto:bor...@gm...
> <mailto:bor...@gm...>>
> >> <mailto:bor...@gm...
> <mailto:bor...@gm...>
> >> <mailto:bor...@gm...
> <mailto:bor...@gm...>>>__]
> >> > Sent: Monday, June 10, 2013 11:33 AM
> >> > To: Stepan Dyatkovskiy; Weddington, Eric
> >> > Cc: avr-llvm-devel@lists.__sourceforge.net
> <http://sourceforge.net>
> >> <mailto:avr...@li...
> <mailto:avr...@li...>>
> >> <mailto:avr-llvm-devel@lists.
> <mailto:avr-llvm-devel@lists.>__sourceforge.net <http://sourceforge.net>
> >> <mailto:avr...@li...
> <mailto:avr...@li...>>>
> >> > Subject: Re: [avr-llvm-devel] Fwd: Sync with trunk
> >> >
> >> > 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.
> >>
> >> All I'm trying to figure out is what would be the
> best VCS
> >> for us to
> >> use (svn or git) in moving over to Atmel Spaces.
> If using
> >> one over
> >> the other makes it easier to do some tasks (like
> staying in
> >> sync
> >> with llvm trunk), then we should go with the one
> that makes
> >> it easier.
> >>
> >> If it doesn't really matter, then I suggest just
> sticking
> >> with svn.
> >>
> >> Eric
> >>
> >>
> >>
> >>
> >
> >
> >
> ------------------------------------------------------------------------------
> > 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...
> <mailto:avr...@li...>
> > 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...
> <mailto:avr...@li...>
> https://lists.sourceforge.net/lists/listinfo/avr-llvm-devel
>
>
|
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X