This project is read-only.
1

Closed

--check-intercepted output inconsistent with tool

description

After running KernelInterceptor on a project in order to obtained the kernel executed and the respective command-line parameters in the .gpuverify folder, if we then attempt to verify the kernel with --check-intercepted, we get failure, without any error message. Verifying the kernel by passing in the arguments via command-line to GPUVerify does not issue any errors and returns a successful verification.

Commit version: e4af4b70e45e+
Note: I have made some modifications to KernelInterceptor, Boogie and GPUVerify, but everything is added, nothing changed.
Closed Mar 4, 2015 at 5:54 PM by jketema
I didn't track down the exact cause of this, but I believe this should no longer occur after my reimplementation of this functionality.

comments

allydonaldson wrote Jun 14, 2014 at 7:16 AM

Can you please attach the .cl file that causes this issue, plus any header files required to process it? (If it's the YorkConcurrency kernel, it's fine to upload it here.)