[LLVMdev] Quad-Core ARMv7 Build Slave Seeks Noble Purpose

[Mikael Lyngvig]

Yes, ARM normally runs as a little-endian and it is a 32-bit CPU.  It CAN
be configured to be a big-endian system, but that requires hardware support
as far as I know.

I do have an old, slow Mac Mini G4 PowerPC (big-endian) that I could hook
up as a builder too.  I was thinking of it the moment you mentioned big
endian.  I actually bought it for testing C++ code on because big-endian
machines are so great at catching those silly errors that we
little-endianers occasionally do.

-- Mikael


2013/11/14 Nick Kledzik <kledzik at apple.com>

>
> On Nov 13, 2013, at 6:17 PM, Sean Silva <chisophugis at gmail.com> wrote:
>
> > What do you want me to build?  LLVM?  Clang?  Both plus test suite?
>>
>> Personally, I see more value in building LLVM, Clang, possibly lld,
>>
>
> I think LLD would especially benefit from testing on other architectures,
> since LLD is the most prone to accidentally having something
> architecture-dependent (e.g. assuming pointers are 64 bits, endianness,
> alignment, etc) and so testing it on more architectures will turn up bugs.
>
>
> Yes, lld reads binary files so gets all the potential bugs that comes with
> that.  Mach-O binary format is challenging because it uses bit fields
> structs and the compiler switches the direction of bit fields on big vs
> little endian archs!
>
> That said, isn’t the ARM machine 32-bit little endian?  Other than
> possible alignment issues, it has the same coverage as i386.   What lld
> needs is big endian build machines.
>
> -Nick
>
>
> _______________________________________________
> 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/20131114/d0ac72c0/attachment.html>