@@ -93,8 +93,8 @@ Implementation of this function is supplied by Native Device Compiler for
93
93
safe approach or by DPCPP Compiler for fallback one.
94
94
95
95
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.
98
98
99
99
100
100
## Safe approach
@@ -103,7 +103,7 @@ This is the preferred approach and implementations should use it when possible.
103
103
It guarantees assertion failure notification delivery to the host regardless of
104
104
kernel behavior which hit the assertion. If backend suports the safe approach,
105
105
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.
107
107
108
108
The Native Device Compiler is responsible for providing implementation of
109
109
`__devicelib_assert_fail` which completely hides details of communication
@@ -128,9 +128,10 @@ The following sequence of events describes how user code gets notified:
128
128
## Fallback approach
129
129
130
130
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.
134
135
135
136
Within this approach, a mutable program scope variable is introduced. This
136
137
variable stores a flag which says if an assert failure was encountered. Fallback
0 commit comments