ispc: Launching compiler without arguments and quitting via Ctrl-C leads to crash

When I launch the compiler without arguments it seems to be waiting for input (which is kind of a weird default). When I try to exit via Ctrl+C then Windows Error Reporting (WER) kicks in because it crashed.

$>ispc.exe
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 "avx2-i32x8".
C:\iusers\ispc_builder\ispc\src\main.cpp(357): 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!
***
<stdin>:1:1: Error: Premature end of file: syntax error, unexpected end of file.

version: v1.12.0, windows, 32bit, downloaded from here: https://ispc.github.io/downloads.html

$ >ispc.exe --version
Intel(r) SPMD Program Compiler (ispc), 1.12.0 (build date Aug 15 2019, LLVM 8.0.0)
Supported Visual Studio versions: Visual Studio 2015 and later.

About this issue

Original URL
State: closed
Created 5 years ago
Comments: 17 (3 by maintainers)

Most upvoted comments

I think waiting for standard input is fine, but crashing when interrupted/canceled is not.

On Oct 17, 2019, at 2:08 AM, Pradeep Kumar notifications@github.com wrote:

Please refer this. It is an intended behaviour

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or unsubscribe.

pbrubaker on Oct 17, 2019

“I vote to admitting that ISPC not an interactive tool and changing this behavior.”

I concur.

On Oct 17, 2019, at 4:37 PM, Dmitry Babokin notifications@github.com wrote:

No other compiler has this behavior Disagree. Launch pyhton 😉

The default of waiting for input is highly questionable. Agree. This was Matt’s experiment, when he envisioned ISPC to be more interactive tool. He wrote about it in his history of ISPC or some other blog posts about ISPC.

I vote to admitting that ISPC not an interactive tool and changing this behavior.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe.

pbrubaker on Oct 18, 2019