Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
SIGILL exceptions using Clang #2367
We have tests as part of the build process and we started getting a lot more failures in our testing suite under Clang after build 129. It appears that Travis switched from Clang 3.3 to 3.4 between (our) builds 129 and 130. Specifically, a lot more SIGFPE and SIGILL exceptions have arisen and the failures have skyrocketed (48 before, 367 after). This same increase was not seen under the gcc build. However, it appears that even Clang 3.3 was producing SIGILL errors under our testing suite as well.
Anyway, seeing SIGILL exceptions suggests that Travis' build of Clang is not generating the correct instructions for the VMs. It's also possible that this is a Clang issue instead, but I'm not seeing much on Google about SIGILL exceptions using Clang. Any insight on this problem would be appreciated, thanks.
We use LLVM's binary package. http://llvm.org/releases/download.html#3.4 If it is error prone, then I tend to think this is an issue with that.
There is a 3.4.1 release; perhaps it will help you. You can wait until we upgrade the VM, or you can grab it from http://llvm.org/releases/3.4.1/clang+llvm-3.4.1-x86_64-unknown-ubuntu12.04.tar.xz, expand it and use it:
before_install: - wget http://llvm.org/releases/3.4.1/clang+llvm-3.4.1-x86_64-unknown-ubuntu12.04.tar.xz - tar xJf clang+llvm-3.4.1-x86_64-unknown-ubuntu12.04.tar.xz - export PATH=$PWD/clang+llvm-3.4.1-x86_64-unknown-ubuntu12.04/bin:$PATH
Yes, but I think they are due to LLVM's design, not the version of Clang
On Mon, Jun 9, 2014 at 10:58 PM, Mathias Meyer firstname.lastname@example.org