Octave OCL Extra Activity
Brought to you by:
tangjinchuan
Activity for Octave OCL Extra
-
Octave OCL Extra released /ocl-1.2.2-AMD-update.tar.gz
-
Tang Jinchuan posted a comment on discussion General Discussion
clinfo
-
Please see the host and kernel project as attached.
-
-
-
-
-
-
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...
-
-
Mesa: It seems that Mesa does not support AMD 5700G GPU due to the fact that its base libclc does not have "gfx909-amdgcn-mesa-mesa3d.bc" file. This will produce a kernel error/segmentation fault with Octave while executing OCL related command. See Mesa_ocl_errors in the attachments. AMDGPU-Pro: This seems to work at the moment. Goto https://www.amd.com/en/support/kb/release-notes/rn-amdgpu-unified-linux-20-40 to download https://drivers.amd.com/drivers/linux/amdgpu-pro-20.40-1147287-sle-15.2.tar.xz...
-
Warning 3: Initializations regarding t_id and t_name Ans: This won’t affect the execution of code. The warnings comes as a result of more strict warnings from clang compiler. It is possible to get rid of the warnings by adding declaration immediately after class. But there would be no difference other than this. Planning to fix this in the future.(octave 7)
-
Warning 1: similar to "ld: warning: direct access in function 'octave_ocl_program::do_multi_index_op(int, octave_value_list const&)' from file 'ocl_ov_program.o' to global weak symbol 'typeinfo for octave_base_ocl_matrix<oclarray<std::__1::complex<double> > >' from file 'ocl_ov_matrix.o' means the weak symbol cannot be overridden at runtime. This was likely caused by different translation units being compiled with different visibility settings."</oclarray<std::__1::complex<double> Ans: Currently,...
-
-
-
1