ClanLib icon indicating copy to clipboard operation
ClanLib copied to clipboard

Assessment of the difficulty in porting CPU architecture for clanlib

Open wangyuliu opened this issue 2 years ago • 1 comments

Hello everyone! I am working on implementing a tool to assess the complexity of CPU architecture porting. It primarily focuses on RISC-V architecture porting. In fact, the tool may have an average estimate of various architecture porting efforts.My focus is on the overall workload and difficulty of transplantation in the past and future,even if a project has already been ported.As part of my dataset, I have collected the clanlib project. I would like to gather community opinions to support my assessment. I appreciate your help and response! Based on scanning tools, the porting complexity is determined to be simple, with a small amount of code related to the CPU architecture in the project. Is this assessment accurate?Do you have any opinions on personnel allocation and consumption time? I look forward to your help and response.

wangyuliu avatar Sep 19 '23 07:09 wangyuliu

It should be straightforward. When I ported ClanLib to Android (as a proof of concept) around 3 years ago, it was trivial to get it to compile on the ARM. It should be the same with RISC-V.

To disable the intel/amd intrinsic optimizations we use the "CL_DISABLE_SSE2" defines in the source code.

It would be worth considering if it's worth the effort. I am unaware of any active open source programs that use the ClanLib library, except my game ( https://github.com/rombust/Methane ) .

rombust avatar Sep 19 '23 10:09 rombust