[LLVMdev] LLC ARM Backend maintainer

Evan Cheng evan.cheng at apple.com
Thu Oct 13 18:23:50 PDT 2011

On Oct 13, 2011, at 11:46 AM, Sandeep Patel wrote:

> Testing on arm-darwin outside of Apple is _complicated_. I had it
> partially working about two years ago.
> The general approach is to use rsh/ssh to remotely execute each test
> on the target, which outside of Apple requires jailbreaking. In the
> old test system, setting up REMOTE_CLIENT=ssh, REMOTE_PORT, etc. would
> automatically use ssh to run the tests. In lit, it looks like
> TestRunner.py has support for external shells that may be intended for
> this purpose; I can't tell. The test-suite and bugpoint code for
> working this way is still present.
> The problem with this setup is that it assumes that the target will be
> running the tests at the same paths as they were built on the host.
> That cannot be achieved outside of Apple because all the NFS
> components are not present in the released/jailbroken iOS. It should
> be straight-forward to build these pieces from the source, but I
> stopped investigating this at this point.

This is the biggest problem. It's obviously a solvable problem but someone will have to devote some resource to it. It's not going to help with 3.0 release, but it will help future releases tremendously.

Any volunteer?


> If somebody else gets this working outside of Apple, please post more
> instructions to the list. I know I felt more comfortable at least
> being able to hand run a few specific tests on arm-darwin against my
> ARM patches before submitting since I was making large changes to
> calling conventions and they are quite different on arm-darwin. Other
> areas of ARM work probably aren't as likely to need to test on
> arm-darwin outside of Apple.
> deep
> On Thu, Oct 13, 2011 at 5:53 PM, Don Quixote de la Mancha
> <quixote at dulcineatech.com> wrote:
>> On Thu, Oct 13, 2011 at 10:33 AM, Raja Venkateswaran
>> <rajav at codeaurora.org> wrote:
>>> I think we need a group of maintainers rather than a single maintainer given
>>> the spectrum of ARM targets/ISAs/platforms required to support
>> There have been a plethora of ARM Instruction Set Architecture
>> variants over the years.  Which ones do we expect LLVM to support
>> right now, and which as-yet unsupported ones do we wish to support?
>> Am I correct that ARM7TDMI is the oldest, slowest core still in use?
>> The Apple iPad 2 and iPhone 4S have the Apple A9 CPU, which I
>> understand is a dual-core Cortex A9.
>> The iPhone 4 and first-generation iPad have the Cortex A8.
>> Xcode gives on the option of targeting either the arm6 or arm7 ISAs,
>> with the recommended build being "Universal" in that the build is done
>> twice with both ISA variants built into the same executable.  I
>> understand older iPhones and iPod Touches support the arm6 but not
>> arm7.
>> Ever Faithful,
>> Don Quixote
>> --
>> Don Quixote de la Mancha
>> Dulcinea Technologies Corporation
>> Software of Elegance and Beauty
>> http://www.dulcineatech.com
>> quixote at dulcineatech.com
>> _______________________________________________
>> LLVM Developers mailing list
>> LLVMdev at cs.uiuc.edu         http://llvm.cs.uiuc.edu
>> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev
> _______________________________________________
> LLVM Developers mailing list
> LLVMdev at cs.uiuc.edu         http://llvm.cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev

More information about the llvm-dev mailing list