<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Admittedly we're very interested in becoming ARM backend maintainers as our product heavily relies on LLVM.<div><br></div><div>However, we don't have testing resources to test both our product and LLVM on a host of target boards. We have some chumbys, beagleboards, iPhones, iPod Touches, tables, Android Phones, etc. And most of those are already booked solid with our own regression tests (most of which are based on llvm-test-suite)</div><div><br></div><div>Could ARM enable us with testing hardware/resources?</div><div><br></div><div>Thanks!</div><div> <br><div apple-content-edited="true">
<span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; ">Joe Abbey<br>Software Architect<br>Arxan Technologies, Inc.<br>1305 Cumberland Ave, Ste 215<br>West Lafayette, IN 47906<br>W: 765-889-4756 x2<br>C: 765-464-9893<br><a href="mailto:jabbey@arxan.com">jabbey@arxan.com</a><br>www.arxan.com<br><br></span>
</div>
<br><div><div>On Oct 13, 2011, at 12:48 PM, Renato Golin wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div>On 11 October 2011 18:22, Anton Korobeynikov <<a href="mailto:anton@korobeynikov.info">anton@korobeynikov.info</a>> wrote:<br><blockquote type="cite">1. We should define which ARM-related features (in general, e.g.<br></blockquote><blockquote type="cite">platforms, cores, modes, etc.) we consider "release important"<br></blockquote><blockquote type="cite">2. We should define the conditions how the features in 1. should be tested<br></blockquote><blockquote type="cite">3. Someone should perform such testing for each release, provide help<br></blockquote><blockquote type="cite">with reproduction of the problems (consider e.g. PR11107, w/o Bill's<br></blockquote><blockquote type="cite">help it would be extremely hard to reproduce the problem, since it<br></blockquote><blockquote type="cite">manifests only on arm/darwin).<br></blockquote><br>4. We should be able to guarantee that release-blocking bugs on ARM<br>targets will be fixed (if technically possible) before the actual<br>release.<br><br>There is no point in define ARM as a release-blocking target if there<br>is no commitment in actually fixing release bugs. What keeps ARM on<br>the bench is just the lack of general commitment. Somebody has to own<br>it, for real.<br><br>cheers,<br>--renato<br>_______________________________________________<br>LLVM Developers mailing list<br><a href="mailto:LLVMdev@cs.uiuc.edu">LLVMdev@cs.uiuc.edu</a> <a href="http://llvm.cs.uiuc.edu">http://llvm.cs.uiuc.edu</a><br><a href="http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev">http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev</a><br></div></blockquote></div><br></div></body></html>