On 3/25/25 10:59, Tobias Burnus wrote:
Updated patch:
+Available properties for an HIP interop object:
+
+@multitable @columnfractions .20 .35 .20 .20
+@headitem Property @tab C data type @tab API routine @tab
value (if constant)
+@item @code{fr_id} @tab @code{omp_interop_fr_t} @tab int @tab
@code{omp_fr_hip}
+@item @code{fr_name} @tab @code{const char *} @tab str @tab
``hip''
+@item @code{vendor} @tab @code{int} @tab int @tab
1
+@item @code{vendor_name} @tab @code{const char *} @tab str @tab
``amd''
+@item @code{device_num} @tab @code{int} @tab int @tab
+@item @code{platform} @tab N/A @tab @tab
+@item @code{device} @tab @code{hipDevice_t} @tab int @tab
+@item @code{device_context} @tab @code{hipCtx_t} @tab ptr @tab
+@item @code{targetsync} @tab @code{hipStream_t} @tab ptr @tab
+@end multitable
That's not what I was suggesting previously. I was asking for
@code{"hip"} etc in the rightmost column if the value is a string
constant. I think you might as well also use @code{1} for the integer
value, too, for consistent formatting and to emphasize that it's a literal.
Likewise for the other similar tables in the patch.
-Sandra
