Troubleshooting

OpenCL program build failed

OpenCL rejected the generated kernel source.

What to check:

• the generated kernel probably compiled from Java successfully, but the OpenCL compiler rejected the emitted C
• look for unsupported constructs in helper bodies, structs, vectors, or backend-specific code
• narrow the kernel down to a smaller reproducer if needed

Failed to compile @GPU method

Compile-time frontend validation failed.

What to check:

• the method may be outside the currently supported Java subset
• the helper call may not be registered as supported GPU-side code
• the struct, pointer, or vector usage may violate the accepted patterns
• enable ABI debug if the failure looks layout-related

GPU execution failed

Runtime setup or argument marshalling failed.

What to check:

• make sure a real backend is installed through GpuRuntime.setBackend(...)
• enable runtime ABI diagnostics
• compare Java-side values with the layout expected by the generated launcher

Windows Gradle File Lock Issues

On Windows, clean test can fail intermittently when Gradle or the OpenCL toolchain still holds files open.

Practical workarounds:

• avoid overlapping Gradle runs in the same workspace
• retry with --no-daemon
• if only clean fails, retry test first to confirm the code itself is fine

See Also

• Runtime Dispatch and ABI