Bruno Pagani

I’d like that too! Maybe could be made as an option?

I, for one, prefer KDE icon actually. But that’s a matter of taste. ;)

That would be very nice. :) This way, you can have a pseudo for random people, your real name for work and family, your habitual nickname for you friends…

The issue is a bit different now with 1.18.0, it has a more specific output: ``` /usr/bin/../lib64/gcc/x86_64-pc-linux-gnu/12.1.0/../../../../include/c++/12.1.0/bits/stl_vector.h:1123: std::vector::reference std::vector::operator[](std::vector::size_type) [_Tp = llvm::Constant *, _Alloc = std::allocator]: Assertion '__n < this->size()'...

OK, thanks from the solution of #2192, I’ve narrowed it down to `-Wp,-D_GLIBCXX_ASSERTIONS` in our `CXXFLAGS`. Per [upstream documentation](https://gcc.gnu.org/onlinedocs/libstdc++/manual/using_macros.html), this >enables extra error checking in the form of precondition assertions,...

(Instructions used to build can be found at https://github.com/archlinux/svntogit-community/blob/packages/ispc/trunk/PKGBUILD, in the `build()` function)

Sorry for the delay, here you go: ``` Warning: No --target specified on command-line. Using default system target "avx2-i32x8". ; ModuleID = 'ispc-1.18.0/tests/lit-tests/llvm_ident.ispc' source_filename = "ispc-1.18.0/tests/lit-tests/llvm_ident.ispc" target datalayout = "e-m:e-p270:32:32-p271:32:32-p272:64:64-i64:64-f80:128-n8:16:32:64-S128"...

So I guess the issue is trying to match `build commit {{[[:xdigit:]]+}}` but no commit is registered on build from release tarballs?

AFAIK, no.

Sorry, I’m not sure what to do from this. Running with `VERBOSE=TRUE`, I just get that the tests are run with `cd /build/ispc/src/build/tests && /usr/bin/python3.8 /build/ispc/src/ispc-1.13.0/utils/lit/lit.py --path=/build/ispc/src/build/bin/. --path=/usr/bin /build/ispc/src/ispc-1.13.0/tests/lit-tests -Dispc_test_exec_root=/build/ispc/src/build/bin/./tests...