[cfe-dev] Semi-regular llvm snapshots for ARMv7/Linux

[İsmail Dönmez]

Ok now I also publish "checked" builds available at
https://i10z.com/llvm/checked/ . These are built on native ARM hardware and
checked using

ninja check check-clang check-libcxx

libcxxabi has a failure and I'll report it before enabling check for it.

But a big fat notice: This ARM hardware might go unavailable any time, so
I'll be publishing my usual cross builds too.


On Sat, Oct 18, 2014 at 10:50 PM, Renato Golin <renato.golin at linaro.org>
wrote:

> On 15 October 2014 12:43, İsmail Dönmez <ismail at donmez.ws> wrote:
> > Sadly these are built on a x86-64 Linux host hence not validated via
> > test-suite. What I currently do is updating llvm snapshot for openSUSE
> and
> > then using that snapshot to build for ARMv7. So far doing only stage1
> > builds. Also using linaro-arm-linux-gnueabihf-4.9 toolchain (September
> 2014
> > release) for headers.
>
> I see. Do you at least run check-all? I wouldn't trust any build that
> doesn't at least passes the basic checks.
>
> One thing you can do to minimise the risk is to only checkout
> revisions that are known to be good by investigating the buildbots.
> That won't guarantee anything, since you're cross-compiling and we're
> not, but that should give you "some" peace of mind.
>
>
> > CC=arm-clang CXX=arm-clang++ cmake -DBUILD_SHARED_LIBS=ON
>
> What revision is this? Release 3.5 or trunk or something else?
>
>
> > CFLAGS="-mfloat-abi=hard -march=armv7-a -mtune=cortex-a8 -mfpu=vfpv3-d16
> > -fuse-ld=gold"
>
> These are sane options. :)
>
> cheers,
> --renato
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/cfe-dev/attachments/20141027/8516fd4b/attachment.html>