You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
File "/nfs/site/home/mkolpako/code/miniconda3/envs/gpu_dev/lib/python3.7/site-packages/numba/core/typeinfer.py", line 1466, in resolve_value_type
raise TypingError(msg, loc=inst.loc)
numba.core.errors.TypingError: Failed in dppy_nopython mode pipeline (step: nopython frontend)
Untyped global name 'get_global_id': Cannot determine Numba type of <class 'function'>
File "l2_distance_kernel.py", line 59:
def l2_distance_kernel(a, b, c):
i = get_global_id(0)
Everything works if I use numba_dppy.get_global_id notation
The text was updated successfully, but these errors were encountered:
Letting users write get_global_id instead of numba_dpex.get_global_id is a syntactic preference IMO. If we want to be more descriptive perhaps we can go the route of numba.cuda and introduce a sycl module and change all of these functions to sycl module.
Having the module qualifier is much better in terms of overall readability and letting users know that the code is specific to the numba_dpex kernel API and will not work outside of the kernel function or without the kernel decorator. I am opening a separate issue #795 to track that work.
Supporting these intrinsic functions directly without using the module name is not going to be added at this moment.
If I try the following code
the following error is risen during typeinfer
Everything works if I use
numba_dppy.get_global_id
notationThe text was updated successfully, but these errors were encountered: