Tang Jinchuan

clinfo

Please see the host and kernel project as attached.

Hi Matt, As I mentioned quite long ago, the code has such problem which can cause AMD problems on some test cases. Now warnings will come with Octave 9.1 on Windows. I think it is time to fix this. Best wishes, Jinchuan In file included from ocl_ov_matrix.h:38, from ocl_ov_matrix_fcns.cc:37: In member function 'OclArray<t>& OclArray<t>::operator=(const OclArray<t>&) [with T = double ', inlined from 'octave_value_list Focl_linspace(const octave_value_list&, int)' at ocl_ov_m atrix_fcns.cc:410:98:...

https://www.amd.com/en/support/kb/faq/amdgpu-installation

Regarding visible settings, with the help of https://www.man7.org/linux/man-pages/man1/ld.1.html and assuming that the release version has no loading problem, we can easily disable ld waring via $(LD) -w --no-warnings $(OBJ_FILES) -o $(TARGET). This will give a clean look and faster experience of the pkg installation. Still, the visible settings have not been solved. Luckily, there seems to be no big deal if our definition on those functions are different from system functions, which is strived to...

Dear Matt, I come back to this question. Since there will be definite asy. workflow breakage. The breakage I encounted is quite normal in cases such as sort algorithms and path searching (still way better than CPU). Then the work is to minize the cost. My thought would be to use a reduced version of nnz to get the size of A<0 in GPU and exchanged the size with host. Then we know what the size of C(B) would be. I did not mean to ask you to implement this for I know your time is very precious. I do...

Bugs reported to apple via developer discussion: https://discussions.apple.com/thread/254494854.

Dear Matt, I was going to report some problems to Apple then I realized one problem maybe due to no defination of field CL_DEVICE_HALF_FP_CONFIG in the spec if I am right. //ocl_context.cc t2.setfield ("fp_config", get_device_prop (device, CL_DEVICE_HALF_FP_CONFIG)); Bad results produced by Mac OS M1: ocl: calling OpenCL function 'clGetDeviceInfo' returned error 'CL_INVALID_OPERATION' (-59). error: OpenCL function call error error: called from ocl_tests at line 85 column 11 Best wishes, Jinchuan...