From: Borja F. <bor...@gm...> - 2012-04-29 17:18:02
|
Ahh so then it's something common to other backends, we can check these failures later on in case we need to fix something. You should be able to compile anything that doesn't use varargs or inline asm (maybe something more i cant remember now), if something is failing it needs to be fixed, that's why i want to get regression tests now, to catch all failures before adding more features. Please repost this email in the regression test thread so we can discuss it there, then i'll reply you in that thread. 2012/4/29 Nicklas Bo Jensen <nbj...@gm...> > Hi, > > Hi, > > First of all I got the exact same test results when building for another > target(msp430 and clean svn checkout of llvm). > > I'm not really sure how far you guys are with the backend, but I have > successfully been able to compile your testcases (/avr-llvm/testcases/*.ll) > to something looking like valid avr assembler. > > I'm a bit confused about: > > - Which device(mmcu) does the generated assembler target? > - How should I test/simulate the assembler? I get errors when trying > to simulate the generated assembler in AVRStudio and cannot process it > using avr-as(e.g. avr-as -mmcu=atmega168 add1.s). > > > Thanks, > Nicklas > > On Tue, Apr 24, 2012 at 2:26 AM, Borja Ferrer <bor...@gm...>wrote: > >> Great! >> >> I have no idea about the tests yet, I've never run the test suite before. >> If they fail with other targets then it's normal, otherwise it'll need to >> be addressed. >> I'll let you some time to play with the backend before really doing some >> work, if you have any doubts ask them here. >> >> >> 2012/4/24 Nicklas Bo Jensen <nbj...@gm...> >> >>> Manually patching llvm/configure and llvm/projects/sample/configure did >>> the trick. Thanks! >>> >>> Are many of the checks supposed to fail when performing make check? >>> (Unexpected Failures: 225) >>> >>> llc seems to be working allright now :) >>> >>> On Mon, Apr 23, 2012 at 11:53 PM, Borja Ferrer <bor...@gm...>wrote: >>> >>>> Ahh ok I didn't receive the message from John, so i thought he never >>>> replied to you. >>>> >>>> No, there's no special revision needed from llvm's repo, it should >>>> always compile with the latest svn revision, I keep our code in sync with >>>> llvm's trunk when any API change occurs, like during the past weekend. >>>> >>>> Remember to add --enable-targets=avr when configuring the build, >>>> probably one of your files got corrupted after patching, try using a fresh >>>> configure (or CMakelists.txt if you're using windows) file and build llvm >>>> without the avr target. If that works then there's the problem, I would >>>> then patch the configure file manually, just search the word msp430 and add >>>> avr the same way it's done. Check other patch files that touch the building >>>> stuff like CMake.diff<http://avr-llvm.svn.sourceforge.net/viewvc/avr-llvm/llvm/trunk/patches/CMake.diff?view=log>and >>>> LLVMBuild.diff<http://avr-llvm.svn.sourceforge.net/viewvc/avr-llvm/llvm/trunk/patches/LLVMBuild.diff?view=log>. >>>> I think the problem is related with one of those, not patches that touch >>>> the sourcecode. >>>> >>>> >>>> 2012/4/23 Nicklas Bo Jensen <nbj...@gm...> >>>> >>>>> Hi, >>>>> >>>>> He did reply to my message: >>>>> On Wed, Apr 11, 2012 at 7:30 PM, John Myers <ato...@gm...> >>>>> wrote: >>>>> >>>>>> Hi Nicklas, >>>>>> >>>>>> Sorry, The getting started page needs to be updated. I've always just >>>>>> applied the patch files one at a time, so I never checked to see if this >>>>>> method works. But I get the same error when trying to apply the patches >>>>>> with ../avr-llvm/patches/*.diff | patch -p0 >>>>>> >>>>>> You can try something like the below instead. >>>>>> echo ../avr-llvm/llvm/trunk/patches/*.diff > patch -p0 >>>>>> >>>>>> >>>>>> --John >>>>> >>>>> >>>>> I ended up applying the patches one by one though, as patch returned >>>>> "**** Only garbage was found in the patch input." when using echo and >>>>> "malformed patch at line 16: Index: CMakeLists.txt" when using cat. >>>>> >>>>> Should any special revision of llvm be checked out? Right now the >>>>> latest revision in the patches is 152169. >>>>> >>>>> I'm getting the following configure error (Regardless of chosen llvm >>>>> revision): >>>>> >>>>> config.status: error: cannot find input file: tools/llvmc/src/ >>>>> Base.td.in >>>>> >>>>> Indeed the file is not there? >>>>> >>>>> I have followed the instructions in: avr-llvm/README and can normally >>>>> compile llvm+clang directly from svn. >>>>> >>>>> BR, >>>>> Nicklas >>>>> >>>>> On Fri, Apr 20, 2012 at 5:06 PM, Borja Ferrer <bor...@gm...>wrote: >>>>> >>>>>> Hello, >>>>>> >>>>>> Please wait for John to reply here about issues with patches since >>>>>> he's the one that usually work with them. >>>>>> >>>>>> CCing John. >>>>>> >>>>>> >>>>>> >>>>>> ------------------------------------------------------------------------------ >>>>>> For Developers, A Lot Can Happen In A Second. >>>>>> Boundary is the first to Know...and Tell You. >>>>>> Monitor Your Applications in Ultra-Fine Resolution. Try it FREE! >>>>>> http://p.sf.net/sfu/Boundary-d2dvs2 >>>>>> _______________________________________________ >>>>>> avr-llvm-devel mailing list >>>>>> avr...@li... >>>>>> https://lists.sourceforge.net/lists/listinfo/avr-llvm-devel >>>>>> >>>>>> >>>>> >>>> >>> >> > |