Dmitry Babokin

This is lit test ``tests/lit-tests/arg_parsing_errors.ispc``. To see how it's compiled you can either run ``make check-all VERBOSE=TRUE``, see the command line to run lit tests, reproduce it and add ``--verbose``...

Now add ``--verbose`` to the command that you posted above, i.e. ``lit.py --path=... ... --verbose`` This way you'll see the exact command line which was executed for the failed test....

Yes, that's it, ``-DISPC_NO_DUMPS=ON`` disables ``--debug-phase=...`` and we don't account for it in lit testing.

You are welcome. I'll keep this issue open to pass information about no-dumps to lit tests. Is it public information about the system you are compiling for? Understanding where and...

Are you using stock build of LLVM or custom built LLVM? If you are using stock LLVM, is there way for using custom built LLVM? Is there a way to...

Do you have pointers to this "one-LLVM rule" (or even better the reasoning behind that)? I still have a feeling that there's misunderstanding here. For ISPC LLVM is not a...

Thanks for the links, they make things more clear. I guess the most important argument is security. But it seems to be not applicable to developer tools / compilers in...

Great post by Chris Lattner on opaque pointers and background of original decision to have high level information in the first place: [link](https://discourse.llvm.org/t/rfc-remove-most-constant-expressions/63179/11). In brief, LLVM IR is considered too...

Looks like a bug.

Here's relationship of different `Module` classes in ISPCRT. `ispcrt::Module` is "handle" class, i.e. it carries a pointer `ispcrt::base::Module`. This is very confusing. I think "handle" classes (same applies for Device,...