Karol Herbst
e2580bded2
Use CL_KERNEL_WORK_GROUP_SIZE more often ( #2435 )
...
Drivers _may_ choose to advertise values for
`CL_DEVICE_MAX_WORK_GROUP_SIZE` or `CL_DEVICE_MAX_WORK_ITEM_SIZES` that
kernels without a `reqd_work_group_size` are not able to be launched
with.
The CTS should therefore make sure that the local_size passed to
`clEnqueueNDRangeKernel` does not exceed `CL_KERNEL_WORK_GROUP_SIZE`
This fixes it up in two places I've noticed this not happening.
2025-08-05 14:40:11 -07:00
..
2025-04-01 09:53:21 -07:00
2025-08-05 14:40:11 -07:00
2024-12-17 08:44:27 -08:00
2025-08-05 09:11:07 -07:00
2025-06-24 15:27:37 -07:00
2025-06-24 08:37:50 -07:00
2025-07-31 12:24:51 +01:00
2025-02-18 09:09:17 -08:00
2025-08-01 21:37:16 +01:00
2025-03-11 21:52:28 +00:00
2025-03-11 21:58:52 +00:00
2025-08-05 09:08:04 -07:00
2023-06-09 11:25:20 +01:00
2021-01-07 11:34:42 +00:00
2025-03-11 21:54:22 +00:00
2025-03-08 22:37:04 +00:00
2024-12-17 09:55:37 -08:00
2025-03-11 21:57:59 +00:00
2025-08-05 17:32:02 +01:00
2025-03-18 17:11:43 +00:00
2025-03-18 17:13:35 +00:00
2025-06-10 08:41:20 -07:00
2023-04-25 19:30:42 +01:00
2025-03-11 22:00:23 +00:00
2025-07-15 16:36:49 -07:00
2025-07-30 18:51:54 +01:00
2025-08-05 09:08:04 -07:00
2025-03-11 21:47:58 +00:00
2025-03-18 17:22:11 +00:00
2025-07-30 18:49:38 +01:00
2025-03-09 09:42:10 +00:00
2025-08-05 09:19:37 -07:00
2025-08-05 14:40:11 -07:00
2025-08-05 09:08:04 -07:00
2025-08-05 09:08:04 -07:00
2025-07-24 10:43:03 -07:00
2025-08-05 09:08:04 -07:00
2025-07-07 16:34:05 -07:00
2025-02-05 13:58:17 +01:00
2025-03-11 21:46:38 +00:00
2024-12-13 16:47:01 +00:00
2025-08-04 11:06:18 +01:00
2025-03-11 22:00:38 +00:00
2025-02-18 20:47:56 -08:00
2023-03-21 09:06:15 -07:00
2019-08-12 10:18:06 +01:00
2019-03-05 16:23:49 +00:00
2024-10-08 09:58:31 -07:00
2024-10-08 09:58:31 -07:00
2024-10-08 09:58:31 -07:00
2024-10-08 09:58:31 -07:00
2024-10-08 09:58:31 -07:00
2020-09-24 20:36:52 +01:00
2024-10-08 09:58:31 -07:00
2024-10-08 09:58:31 -07:00
2022-10-03 14:26:43 +01:00
2022-02-22 16:49:35 +00:00