[LLVMdev] Some blogged LLVM experience.

[Ralph Corderoy]

Hi Duncan,

> "The bad news comes with the make test-all results.  Less than two
> minutes into the comprehensive test suite the LLVM-GCC version of Ruby
> 1.9 dies with the following message: "Illegal instruction (core
> dumped)". Later it tells me the test failed with "error 132". This is,
> as you can see, not a very useful message since it's not really
> helping me locate where the error is."
> 
> The illegal instruction message is not coming from ruby or LLVM, it is
> coming from the OS: the program fed the processor some garbage to
> execute rather than proper instruction codes, and was promptly killed
> with this message.  As for "error 132", it is also not coming from
> LLVM which does not produce messages of this kind.

132 is 0x84 and looks like an exit value for the process, i.e. it was
killed by signal 4 which is normally SIGILL, i.e. illegal instruction.
The test harness is probably printing the `error 132'.

Cheers,


Ralph.