(In reply to Jan Vesely from comment #9)
> (In reply to Maciej S. Szmigiero from comment #8)
> > Aren't program@execute@calls-struct and program@execu=
te@tail-calls tests
> > from comment 4 exampl=
es of this behavior?
> > These seem to run but return wrong results, or am I not parsing t=
he piglit
> > test results correctly?
>=20
> This is more of a piglit problem. piglit uses a combination of enqueue=
 and
> clFinish. However, the error happens on kernel launch. thus;
> 1.) clEnqueueNDRangeKernel -- success
> 2.) The driver tries to launch the kernel and fails on relocations
> 3.) application(piglit) calls clFinish
>=20
> depending on the order of 2. and 3. clFinish can either see an empty q=
ueue
> and succeed or try to wait for kernel execution and fail.
>=20
> The following series should address that:
> https://pa=
tchwork.freedesktop.org/series/52857/

Thanks for the detailed explanation and the patches.

I can confirm that with them applied program@execute@calls-struct a=
nd
program@execute@tail-calls exit with
CL_EXEC_STATUS_ERROR_FOR_EVENTS_IN_WAIT_LIST, so I guess they work
(or rather, fail) as expected.

Feel free to add
"Tested-by: Maciej S. Szmigiero <mail@maciej.szmigiero.name>" tag if you wou=
ld
like.