Skip to content

Commit 87e9fa7

Browse files
authored
[SYCL][DOC] Fix a typo in assert doc (#4674)
PI_INTEL_DEVICELIB_CASSERT -> PI_DEVICE_INFO_EXTENSION_DEVICELIB_ASSERT Signed-off-by: Dmitry Sidorov <[email protected]>
1 parent c661d85 commit 87e9fa7

File tree

1 file changed

+7
-6
lines changed

1 file changed

+7
-6
lines changed

sycl/doc/Assert.md

Lines changed: 7 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -93,8 +93,8 @@ Implementation of this function is supplied by Native Device Compiler for
9393
safe approach or by DPCPP Compiler for fallback one.
9494
9595
In order to distinguish which implementation to use, DPCPP Runtime checks for
96-
`PI_INTEL_DEVICELIB_CASSERT` extension. If the extension isn't available, then
97-
fallback implementation is used.
96+
`PI_DEVICE_INFO_EXTENSION_DEVICELIB_ASSERT` extension. If the extension isn't
97+
available, then fallback implementation is used.
9898
9999
100100
## Safe approach
@@ -103,7 +103,7 @@ This is the preferred approach and implementations should use it when possible.
103103
It guarantees assertion failure notification delivery to the host regardless of
104104
kernel behavior which hit the assertion. If backend suports the safe approach,
105105
it must report this capability to DPCPP Runtime via the
106-
`PI_INTEL_DEVICELIB_CASSERT` extension query.
106+
`PI_DEVICE_INFO_EXTENSION_DEVICELIB_ASSERT` extension query.
107107
108108
The Native Device Compiler is responsible for providing implementation of
109109
`__devicelib_assert_fail` which completely hides details of communication
@@ -128,9 +128,10 @@ The following sequence of events describes how user code gets notified:
128128
## Fallback approach
129129
130130
If Device-side Runtime doesn't support `__devicelib_assert_fail` (as reported
131-
via `PI_INTEL_DEVICELIB_CASSERT` extension query) then a fallback approach comes
132-
in place. The approach doesn't require any support from Device-side Runtime and
133-
Native Device Compiler. Neither it does from Low-level Runtime.
131+
via `PI_DEVICE_INFO_EXTENSION_DEVICELIB_ASSERT` extension query) then a fallback
132+
approach comes in place. The approach doesn't require any support from
133+
Device-side Runtime and Native Device Compiler. Neither it does from Low-level
134+
Runtime.
134135
135136
Within this approach, a mutable program scope variable is introduced. This
136137
variable stores a flag which says if an assert failure was encountered. Fallback

0 commit comments

Comments
 (0)