From ec5ca5d58fa5c2b7adc4e877870015ddfaf5ab31 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Andreas=20Kl=C3=B6ckner?= <inform@tiker.net>
Date: Mon, 21 Oct 2019 16:48:18 +0200
Subject: [PATCH] Remove disputed note about read-after-read sync, gh-303
---
pyopencl/array.py | 6 ------
1 file changed, 6 deletions(-)
diff --git a/pyopencl/array.py b/pyopencl/array.py
index 72d2a0cf..9f2cb675 100644
--- a/pyopencl/array.py
+++ b/pyopencl/array.py
@@ -376,12 +376,6 @@ class Array(object):
care of its own operation ordering. The facilities in this section make
this possible.
- .. note::
-
- Currently, read and write events are not distinguished.
- As a result, e.g., read-only operations will needlessly wait on other
- read-only operations (i.e., executed among asynchronous queues).
-
.. versionadded:: 2014.1.1
.. attribute:: events
--
GitLab