Menu
▾
▴
avr-llvm-devel
|
From: Borja F. <bor...@gm...> - 2010-10-10 12:01:10
|
Hello, i've just finished updating my code to the new LLVM version released some days ago, after this I've merged it to your codebase making the appropiate changes. As a start i decided to commit it to a branch before touching trunk so you can take a look and test it. To build it, just download the LLVM source code, apply the patches to Triple.h/cpp and build it. Let me know your thoughts. |
|
From: John M. <ato...@gm...> - 2010-10-12 02:51:01
|
On Sun, Oct 10, 2010 at 5:01 AM, Borja Ferrer <bor...@gm...> wrote: > Hello, i've just finished updating my code to the new LLVM version released > some days ago, after this I've merged it to your codebase making the > appropriate changes. As a start i decided to commit it to a branch before > touching trunk so you can take a look and test it. > To build it, just download the LLVM source code, apply the patches to > Triple.h/cpp and build it. > > Let me know your thoughts. > > Hi Borja, I think it's OK to start merging your *branch* into the *trunk*. I've successfully built it on Linux and Windows and played around with it a little bit. --John |
|
From: Borja F. <bor...@gm...> - 2010-10-12 11:20:27
|
Nice, what do you think about the generated code? Let me ask you an unrelated question, how have you set up the backend code having the LLVM source code out of SVN? 2010/10/12 John Myers <ato...@gm...> > > > On Sun, Oct 10, 2010 at 5:01 AM, Borja Ferrer <bor...@gm...>wrote: > >> Hello, i've just finished updating my code to the new LLVM version >> released some days ago, after this I've merged it to your codebase making >> the appropriate changes. As a start i decided to commit it to a branch >> before touching trunk so you can take a look and test it. >> >> To build it, just download the LLVM source code, apply the patches to >> Triple.h/cpp and build it. >> >> Let me know your thoughts. >> >> > Hi Borja, > > I think it's OK to start merging your *branch* into the *trunk*. > I've successfully built it on Linux and Windows and played around with it a > little bit. > > > > --John > |
|
From: Josef E. <za...@za...> - 2010-10-12 13:37:58
|
Hello and a welcome from my side. On 10/12/2010 01:20 PM, Borja Ferrer wrote: > Nice, what do you think about the generated code? > > Let me ask you an unrelated question, how have you set up the backend > code having the LLVM source code out of SVN? There is some documentation (gettingstarted.html, devel.html) in the doc folder (llvm/trunk/docs/). I think thats what you are looking for. BR Josef > > 2010/10/12 John Myers <ato...@gm... > <mailto:ato...@gm...>> > > > > On Sun, Oct 10, 2010 at 5:01 AM, Borja Ferrer <bor...@gm... > <mailto:bor...@gm...>> wrote: > > Hello, i've just finished updating my code to the new LLVM > version released some days ago, after this I've merged it to > your codebase making the appropriate changes. As a start i > decided to commit it to a branch before touching trunk so you > can take a look and test it. > > To build it, just download the LLVM source code, apply the > patches to Triple.h/cpp and build it. > > Let me know your thoughts. > > > Hi Borja, > > I think it's OK to start merging your /branch/ into the /trunk/. > I've successfully built it on Linux and Windows and played around > with it a little bit. > > > > --John > > > > > ------------------------------------------------------------------------------ > Beautiful is writing same markup. Internet Explorer 9 supports > standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3. > Spend less time writing and rewriting code and more time creating great > experiences on the web. Be a part of the beta today. > http://p.sf.net/sfu/beautyoftheweb > > > > _______________________________________________ > avr-llvm-devel mailing list > avr...@li... > https://lists.sourceforge.net/lists/listinfo/avr-llvm-devel |
|
From: John M. <ato...@gm...> - 2010-10-12 17:56:49
|
On Tue, Oct 12, 2010 at 4:20 AM, Borja Ferrer <bor...@gm...> wrote: > Nice, what do you think about the generated code? > > It looks good. I haven't tried out anything fancy yet, just some of the files in the* /trunk/testcases*. Let me ask you an unrelated question, how have you set up the backend code > having the LLVM source code out of SVN? > > I'm not sure what you mean? Are you asking how I setup the src code for building the compiler? The source code I build is still under SVN control I just checkout */llvm/tags/release_28* and then checkout the AVR branch into*lib/Target/ *. On Windows I actually checkout the whole avr-llvm and then make a directory junction link (mklink /J) into *lib/Target/*. > 2010/10/12 John Myers <ato...@gm...> > > >> >> On Sun, Oct 10, 2010 at 5:01 AM, Borja Ferrer <bor...@gm...>wrote: >> >>> Hello, i've just finished updating my code to the new LLVM version >>> released some days ago, after this I've merged it to your codebase making >>> the appropriate changes. As a start i decided to commit it to a branch >>> before touching trunk so you can take a look and test it. >>> >>> To build it, just download the LLVM source code, apply the patches to >>> Triple.h/cpp and build it. >>> >>> Let me know your thoughts. >>> >>> >> Hi Borja, >> >> I think it's OK to start merging your *branch* into the *trunk*. >> I've successfully built it on Linux and Windows and played around with it >> a little bit. >> >> >> >> --John >> > > > > ------------------------------------------------------------------------------ > Beautiful is writing same markup. Internet Explorer 9 supports > standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3. > Spend less time writing and rewriting code and more time creating great > experiences on the web. Be a part of the beta today. > http://p.sf.net/sfu/beautyoftheweb > _______________________________________________ > avr-llvm-devel mailing list > avr...@li... > https://lists.sourceforge.net/lists/listinfo/avr-llvm-devel > > |
|
From: Borja F. <bor...@gm...> - 2010-10-12 18:25:57
|
Thanks Josef, that was exactly what i was looking for, btw, i dont know why i didnt receive your email, had to read it through SF. John basically I wanted to know how you managed here to build the backend having the code repository outside the LLVM source tree, thanks for the info. For now im working with llvm-gcc instead of clang in linux, didnt want to mix things for now, so i went with the easiest thing. This means that data type sizes arent going to match the AVR ABI for me in a while, but i think this shouldnt be a problem since we're not writing AVR code. So now that the code is there (going to wait 2 more days until we merge it into trunk incase you find anything that has to be changed), i guess we should proceed in planning how to continue the work. |
|
From: John M. <ato...@gm...> - 2010-10-15 18:53:47
|
On Tue, Oct 12, 2010 at 11:25 AM, Borja Ferrer <bor...@gm...>wrote: > ... > > So now that the code is there (going to wait 2 more days until we merge it > into trunk incase you find anything that has to be changed), i guess we > should proceed in planning how to continue the work. > > This is how I see the merge happening so far after comparing the branches. /AVR/TargetInfo/AVRTargetInfo.cpp := ~same /AVR/AsmPrinter/AVRAsmPrinter.cpp := trunk has more AVR specific stuff /AVR/AVR.td := ~same /AVR/AVR.h := ~same /faluco/AVR/AVR16bitInstPass.cpp := mv to trunk /AVR/AVRCallingConv.td := use faluco /AVR/AVRInstrFormats.td := use faluco /AVR/AVRInstrInfo.cpp|h := use faluco, add any useful stuff from trunk /AVR/AVRInstrInfo.td := use faluco, merge predicates from trunk /AVR/AVRISelDAGToDAG.cpp := use faluco /AVR/AVRISelLowering.cpp|h := use faluco /AVR/AVRMCAsmInfo.cpp|h := merge /AVR/AVRRegisterInfo.cpp|h := merge /AVR/AVRRegisterInfo.td := use faluco /AVR/AVRSelectionDAGInfo.cpp|h := mv to trunk /AVR/AVRSubtarget.cpp|h := use trunk, merge for consistency /AVR/AVRTargetMachine.cpp|h := use faluco |
|
From: Borja F. <bor...@gm...> - 2010-10-15 19:48:07
|
About all the Asmprinter stuff, trunk's wont compile because many things have changed in the Asmprinter stuff during this release, so i didnt bothered touching it. In fact, my asmprinter code is a direct copy of another target without any customization (there's a big note at the top of the cpp file about this). Basically, i decided to leave this part for later on until codegen was more developed. You may want to take a look into this. Gah i have to leave, i'll continue commenting later. 2010/10/15 John Myers <ato...@gm...> > > > On Tue, Oct 12, 2010 at 11:25 AM, Borja Ferrer <bor...@gm...>wrote: > >> ... >> >> >> So now that the code is there (going to wait 2 more days until we merge it >> into trunk incase you find anything that has to be changed), i guess we >> should proceed in planning how to continue the work. >> >> > This is how I see the merge happening so far after comparing the branches. > > /AVR/TargetInfo/AVRTargetInfo.cpp := ~same > > /AVR/AsmPrinter/AVRAsmPrinter.cpp := trunk has more AVR specific stuff > > /AVR/AVR.td := ~same > /AVR/AVR.h := ~same > > /faluco/AVR/AVR16bitInstPass.cpp := mv to trunk > > /AVR/AVRCallingConv.td := use faluco > /AVR/AVRInstrFormats.td := use faluco > > /AVR/AVRInstrInfo.cpp|h := use faluco, add any useful stuff > from trunk > > /AVR/AVRInstrInfo.td := use faluco, merge predicates from > trunk > > > /AVR/AVRISelDAGToDAG.cpp := use faluco > /AVR/AVRISelLowering.cpp|h := use faluco > > /AVR/AVRMCAsmInfo.cpp|h := merge > /AVR/AVRRegisterInfo.cpp|h := merge > > /AVR/AVRRegisterInfo.td := use faluco > > /AVR/AVRSelectionDAGInfo.cpp|h := mv to trunk > > /AVR/AVRSubtarget.cpp|h := use trunk, merge for consistency > > /AVR/AVRTargetMachine.cpp|h := use faluco > |
|
From: Borja F. <bor...@gm...> - 2010-10-16 12:05:35
|
Hello John, i've just merged into the branch more useful code from trunk, let me know if you're ok with that so that we can merge it into trunk. Does your changes to Asmprinter compile and build so i can merge them into the branch, or do they need more work? |
|
From: John M. <ato...@gm...> - 2010-10-16 19:41:24
|
On Sat, Oct 16, 2010 at 5:05 AM, Borja Ferrer <bor...@gm...> wrote: > Hello John, i've just merged into the branch more useful code from trunk, > let me know if you're ok with that so that we can merge it into trunk. Does > your changes to Asmprinter compile and build so i can merge them into the > branch, or do they need more work? > > Hi Borja, I'm OK with merging that into trunk. I've updated the files in */trunk/AVR/AsmPrinter* so now they compile/build against version 2.8. --John |
|
From: Borja F. <bor...@gm...> - 2010-10-16 21:14:39
|
Excellent, i'm about to commit the changes into trunk. Another thing to mention is that after merging your changes in asmprinter i noticed that symbol names dont get printed in the asm file anymore. For example try making a function call and you'll notice you get call instead of call foo 2010/10/16 John Myers <ato...@gm...> > > > On Sat, Oct 16, 2010 at 5:05 AM, Borja Ferrer <bor...@gm...>wrote: > >> Hello John, i've just merged into the branch more useful code from trunk, >> let me know if you're ok with that so that we can merge it into trunk. Does >> your changes to Asmprinter compile and build so i can merge them into the >> branch, or do they need more work? >> >> > Hi Borja, > I'm OK with merging that into trunk. > I've updated the files in */trunk/AVR/AsmPrinter* so now they > compile/build against version 2.8. > > --John > > |
|
From: Borja F. <bor...@gm...> - 2010-10-16 21:42:15
|
Ok code commited, i guess having this done now, we should move on in discussing and planning some development. 2010/10/16 Borja Ferrer <bor...@gm...> > Excellent, i'm about to commit the changes into trunk. Another thing to > mention is that after merging your changes in asmprinter i noticed that > symbol names dont get printed in the asm file anymore. For example try > making a function call and you'll notice you get > call > instead of > call foo > > 2010/10/16 John Myers <ato...@gm...> > > >> >> On Sat, Oct 16, 2010 at 5:05 AM, Borja Ferrer <bor...@gm...>wrote: >> >>> Hello John, i've just merged into the branch more useful code from trunk, >>> let me know if you're ok with that so that we can merge it into trunk. Does >>> your changes to Asmprinter compile and build so i can merge them into the >>> branch, or do they need more work? >>> >>> >> Hi Borja, >> I'm OK with merging that into trunk. >> I've updated the files in */trunk/AVR/AsmPrinter* so now they >> compile/build against version 2.8. >> >> --John >> >> > |
|
From: John M. <ato...@gm...> - 2010-10-18 02:41:11
|
On Sat, Oct 16, 2010 at 2:14 PM, Borja Ferrer <bor...@gm...> wrote: > Excellent, i'm about to commit the changes into trunk. Another thing to > mention is that after merging your changes in asmprinter i noticed that > symbol names dont get printed in the asm file anymore. For example try > making a function call and you'll notice you get > call > instead of > call foo > Oops, that was a copy/paste error. I deleted a line by accident in AVRInstPrinter.cpp. |
×
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