For what it's worth, test_fpu_setup() tests creating a D3D device with a custom FPU control word. (The background on that is that creating a D3D device should setup the FPU in a specific way, depending on if D3DCREATE_FPU_PRESERVE is specified or not.) My guess would be that something in llvm doesn't expect to be called with a non-default FPU control word.