FS#60340 - [ispc] 1.9.2 crashes on any input
Attached to Project:
Community Packages
Opened by Jonas Karlsson (jonask) - Sunday, 07 October 2018, 18:31 GMT
Last edited by Doug Newgard (Scimmia) - Monday, 10 December 2018, 18:29 GMT
Opened by Jonas Karlsson (jonask) - Sunday, 07 October 2018, 18:31 GMT
Last edited by Doug Newgard (Scimmia) - Monday, 10 December 2018, 18:29 GMT
|
Details
Description:
ispc 1.9.2 crashes on any input. Additional info: Using package ispc 1.9.2-4. Steps to reproduce: Just running ispc without any input. Below shows the output: jonas@x220 ~> ispc Warning: No output file or header file name specified. Program will be compiled and warnings/errors will be issued, but no output will be generated. Warning: No --target specified on command-line. Using default system target "avx1-i32x8". main.cpp(235): FATAL ERROR: Unhandled signal sent to process; terminating. *** *** Please file a bug report at https://github.com/ispc/ispc/issues *** (Including as much information as you can about how to reproduce this error). *** You have apparently encountered a bug in the compiler that we'd like to fix! *** fish: “ispc” terminated by signal SIGABRT (Abort) |
This task depends upon
Closed by Doug Newgard (Scimmia)
Monday, 10 December 2018, 18:29 GMT
Reason for closing: Fixed
Additional comments about closing: ispc 1.9.2-5
Monday, 10 December 2018, 18:29 GMT
Reason for closing: Fixed
Additional comments about closing: ispc 1.9.2-5
Or was it not supposed to abort when it had nothing to do?
jonas@x220 ~/D/ispc-v1.9.2-linux> ./ispc mandelbrot.ispc -o out --target avx
jonas@x220 ~/D/ispc-v1.9.2-linux> /usr/bin/ispc mandelbrot.ispc -o out --target avx
main.cpp(235): FATAL ERROR: Unhandled signal sent to process; terminating.
***
*** Please file a bug report at https://github.com/ispc/ispc/issues
*** (Including as much information as you can about how to reproduce this error).
*** You have apparently encountered a bug in the compiler that we'd like to fix!
***
fish: “/usr/bin/ispc mandelbrot.ispc -…” terminated by signal SIGABRT (Abort)
The same problem appears to have come up elsewhere: https://groups.google.com/forum/#!msg/llvm-dev/8Tcz49kTNCw/NI0l_MiZAwAJ
For now, I believe it's best to compile ispc with gcc. I don't see an accepted fix for this upstream yet.
I’m rebuilding ispc with gcc for the time being, but I’m wondering if building clang/llvm with clang wouldn’t make much more sense…
I'd rather not have to rebuild all packages linking to LLVM, and possibly still have the same problem afterwards (but in reverse).