> Both A9 bots are running the same Ubuntu (13.03), with the same GCC (4.7.2), > and are the same hardware (Panda ES RevB), so it really strikes me as odd > that we have such a different behaviour between them.Hmm. I'll see what I can do on my tablet (not tried building LLVM there before so it could take a while), it seems like there are *some* failures everywhere. If we're lucky it'll just be a matter of fixing the PR16013 that David reported. Tim.
Remote mcjit has never worked on arm. By removing the assertion, we're no longer seeing deterministic failures. I think by fixing PR16013 we'll enable support for remote mcjit on arm, and can then remove the xfails altogether. In the meantime, marking the tests as unsupported seems to be the best option. I don't have a machine for a few days but I can take a look at finally cleaning up resolveRelocations() next week. Amara> Both A9 bots are running the same Ubuntu (13.03), with the same GCC(4.7.2),> and are the same hardware (Panda ES RevB), so it really strikes me as odd > that we have such a different behaviour between them.Hmm. I'll see what I can do on my tablet (not tried building LLVM there before so it could take a while), it seems like there are *some* failures everywhere. If we're lucky it'll just be a matter of fixing the PR16013 that David reported. Tim. _______________________________________________ LLVM Developers mailing list LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20130518/a9f02cd5/attachment.html>
On 18 May 2013 17:42, Amara Emerson <amara.emerson at gmail.com> wrote:> In the meantime, marking the tests as unsupported seems to be the best > option. I don't have a machine for a few days but I can take a look at > finally cleaning up resolveRelocations() next week. >As opposed to what the docs say, ; UNSUPPORTED: arm has no effect. The only way I know how to make it work is to move them to a separate dir and mark the dir as unsupported for ARM, but that's not a good temporary solution. --renato -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20130518/6afcc7ee/attachment.html>
Thanks for looking at this Tim. On a pandaboard, at least with the Release+Asserts config I tried, those tests do complain on stderr but llvm-lit thinks they've passed/expected fails, they don't actually count as fails like they do on the buildbot. Regarding solving PR16013 that looks like a relatively tractable job (on both 32-bit arm and aarch64) IF you're already familiar with the implications of what the instruction set does; unfortunately that set doesn't include me... Cheers, Dave ________________________________________ From: Tim Northover [t.p.northover at gmail.com] Sent: Saturday, May 18, 2013 4:53 PM To: Renato Golin Cc: Amara Emerson; David Tweed; LLVM Dev Subject: Re: [LLVMdev] Unsupported MCJIT tests on ARM?> Both A9 bots are running the same Ubuntu (13.03), with the same GCC (4.7.2), > and are the same hardware (Panda ES RevB), so it really strikes me as odd > that we have such a different behaviour between them.Hmm. I'll see what I can do on my tablet (not tried building LLVM there before so it could take a while), it seems like there are *some* failures everywhere. If we're lucky it'll just be a matter of fixing the PR16013 that David reported. Tim. -- IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
On 18 May 2013 19:29, David Tweed <David.Tweed at arm.com> wrote:> Regarding solving PR16013 that looks like a relatively tractable job (on > both 32-bit arm and aarch64) IF you're already familiar with the > implications of what the instruction set does; unfortunately that set > doesn't include me... >Hi David, I'll move all remote tests to a dir and mark them unsupported for now. What about the ExecutionEngine unittest below? Can you fix it? Or disable it on ARM? http://lab.llvm.org:8011/builders/llvm-armv5-linux/builds/298/steps/test-llvm/logs/LLVM-Unit%20%3A%3A%20ExecutionEngine__MCJIT____wd__buildbot__llvm-armv5-linux__llvm__unittests__ExecutionEngine__MCJIT__Debug%2BAsserts__MCJITTests__MCJITTest.return_global cheers, --renato -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20130518/3e5506b9/attachment.html>