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.