OpenCL 3.1.1 Released To Address A Possible Performance Regression
OpenCL 3.1.1 has been released to address a potential performance regression identified in OpenCL 3.1. This point release reverts the behavior of clGetEventInfo to its OpenCL 3.0 semantics, which avoids unnecessary host synchronization. The update also includes reserved enum blocks for future Intel and Qualcomm extensions and minor fixes.
- ▪OpenCL 3.1.1 focuses on addressing a performance regression from OpenCL 3.1.
- ▪The release reverts clGetEventInfo behavior to match OpenCL 3.0 to avoid performance issues.
- ▪The update reserves enum blocks for upcoming Intel and Qualcomm extensions.
Phoronix files mainly under tech. We currently carry 325 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | Phoronix |
| Canonical URL | https://www.phoronix.com/news/OpenCL-3.1.1-Released |
| Publication time | Fri, 22 May 2026 12:29:13 -0400 |
| Retrieval time | 2026-05-22T16:37:02.520Z |
| Last seen | 2026-05-22T16:37:02.520Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | 9D08qkQ7lZpG |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
OpenCL 3.1.1 Released To Address A Possible Performance Regression Written by Michael Larabel in Standards on 22 May 2026 at 12:29 PM EDT. Add A Comment Released earlier this month was the OpenCL 3.1 specification with a focus on enhancing AI and HPC workloads for this long-time Khronos specification. Out today is OpenCL 3.1.1 as a point release with an emphasis on addressing a possible performance regression of OpenCL 3.1. OpenCL 3.1.1 reverts the short-lived OpenCL 3.1 behavior of clGetEventInfo returning CL_COMPLETE as a host synchronization point. Those wanting a host synchronization point should instead call a function waiting on the OpenCL event instead like with clWaitForEvents.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Phoronix.