From 0ceca78879ec0f057f6f5340ff55d6092f26f2d2 Mon Sep 17 00:00:00 2001
From: 1sgtpepper <165563006+1sgtpepper@users.noreply.github.com>
Date: Thu, 29 Oct 2026 00:56:01 +0800
Subject: [PATCH] Clarify negative user-event status consequences

---
 api/opencl_runtime_layer.asciidoc | 11 +++++++++++
 1 file changed, 11 insertions(+)

diff --git a/api/opencl_runtime_layer.asciidoc b/api/opencl_runtime_layer.asciidoc
index 13d0756ef..1d1dc977f 100644
--- a/api/opencl_runtime_layer.asciidoc
+++ b/api/opencl_runtime_layer.asciidoc
@@ -12489,6 +12489,17 @@ include::{generated}/api/version-notes/clSetUserEventStatus.asciidoc[]
     {clSetUserEventStatus} can only be called once to change the execution
     status of _event_.
 
+[NOTE]
+====
+When an enqueued command waiting on _event_ is terminated by a negative
+_execution_status_, its command-queue and associated context (including all
+other command-queues in that context) may no longer be available.
+The behavior of subsequent OpenCL API calls that use this context or its
+command-queues is implementation-defined.
+The callback function specified when the context was created can be used
+to report appropriate error information.
+====
+
 [NOTE]
 ====
 If there are enqueued commands with user events in the _event_wait_list_