Associate queue with device in context (#1992)

Making a native queue doesn't require hDevice to be non null, but this
associates the queue with a null device, even if hContext contains valid
devices.

This fixes the behaviour for a single device context, making the queue
be associated with the only device in the context. But there is a
question mark over whether this entry point makes sense for a multi
device UR context. Should we be able to construct a queue with a native
queue without knowing what the UR device associated with the queue is?
Probably not.

Co-authored-by: aarongreig <aaron.greig@codeplay.com>

Author: Hugh Delaney

source/adapters/cuda/queue.cpp

@@ -265,7 +265,8 @@ UR_APIEXPORT ur_result_t UR_APICALL urQueueCreateWithNativeHandle(
     ur_native_handle_t hNativeQueue, ur_context_handle_t hContext,
     ur_device_handle_t hDevice, const ur_queue_native_properties_t *pProperties,
     ur_queue_handle_t *phQueue) {
-  (void)hDevice;
+  if (!hDevice && hContext->getDevices().size() == 1)
+    hDevice = hContext->getDevices().front();
 
   unsigned int CuFlags;
   CUstream CuStream = reinterpret_cast<CUstream>(hNativeQueue);

source/adapters/hip/queue.cpp

@@ -299,7 +299,8 @@ UR_APIEXPORT ur_result_t UR_APICALL urQueueCreateWithNativeHandle(
     ur_native_handle_t hNativeQueue, ur_context_handle_t hContext,
     ur_device_handle_t hDevice, const ur_queue_native_properties_t *pProperties,
     ur_queue_handle_t *phQueue) {
-  (void)hDevice;
+  if (!hDevice && hContext->getDevices().size() == 1)
+    hDevice = hContext->getDevices().front();
 
   unsigned int HIPFlags;
   hipStream_t HIPStream = reinterpret_cast<hipStream_t>(hNativeQueue);