shouldn't the first hash be 128 hex characters (instead of 64) ? Just test with "echo -n hashcat | sha512sum", it is exactly 128 hex chars long.
you would also need to test if the salt needs to be swapped etc
for instance I see sha512_update_global_swap () used in the unmodified -m 1720 kernel.
The COMPARE_M_SCALAR is also suspicous ... why would you test with multiple (2+) hashes first ? use the sxx kernel function for single (1 only) hash and COMPARE_S_SCALAR to compare...
for testing you should also always make sure to remove the cached kernel folder (kernels/).
These are just a few hints, didn't look carefully at the code yet
It would make sense to use printf () for debugging/troubleshooting and maybe an (Intel) CPU with Intel OpenCL Runtime installed (it's probably the easiest to test and debug with printf ()).
you would also need to test if the salt needs to be swapped etc
for instance I see sha512_update_global_swap () used in the unmodified -m 1720 kernel.
The COMPARE_M_SCALAR is also suspicous ... why would you test with multiple (2+) hashes first ? use the sxx kernel function for single (1 only) hash and COMPARE_S_SCALAR to compare...
for testing you should also always make sure to remove the cached kernel folder (kernels/).
These are just a few hints, didn't look carefully at the code yet
It would make sense to use printf () for debugging/troubleshooting and maybe an (Intel) CPU with Intel OpenCL Runtime installed (it's probably the easiest to test and debug with printf ()).