Readme should mention that this crashes with SIGILL if the CPU doesn't have AVX

[mtmkls]

This is what I see in gdb:
Reading symbols from /usr/bin/fwlauncher.bin-0.1...
(No debugging symbols found in /usr/bin/fwlauncher.bin-0.1)
[New LWP 478567]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by `/usr/bin/fwlauncher.bin-0.1 "/usr/share/sight/VRRender-0.9/profile.xml"'.
Program terminated with signal SIGILL, Illegal instruction.
#0 0x00007f40e92b5b93 in ?? () from /usr/lib/x86_64-linux-gnu/sight/libfwTools.so.0
(gdb) l
1 ../sysdeps/x86_64/crti.S: No such file or directory.
(gdb) display/i $pc
1: x/i $pc
=> 0x7f40e92b5b93: vmovq %r13,%xmm1

[dweckmann]

Hi @mtmkls,

You are indeed right.

We choose to take advantage of AVX instruction set by default, because it is available since 2008, and now, 13 years later, people who use hardware that doesn't support it, are quite rare. We even tough we were conservative as we planned to use AVX2.

Fortunately, you can change this compile flag quite easily, on the new released code base (Sight 21.0), just edit the file https://github.com/IRCAD/sight/blob/master/cmake/build/flags.cmake and replace -march=sandybridge with something older like the generic -march=x86-64. For Windows, simply remove the /AVX flag. Of course, a slight impact on performance is possible.

BTW, we acknowledge the suggestion to add a clearer hardware requirement in the README.

Thanks for reporting !

[fbridault]

I'll keep this open until we add the mention in the README.

[schweitzer]

Seems fixed please see https://github.com/IRCAD/sight#hardware--operating-system--compiler-support