openexr icon indicating copy to clipboard operation
openexr copied to clipboard

Assessment of the difficulty in porting CPU architecture for openexr

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, it can be estimated on average across various architectures.My focus is on the overall workload and difficulty of transplantation in the past and future.As part of my dataset, I have collected the openexr 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 moderate, with a small amount of code related to the CPU architecture in the project. What kind of developer configuration or team setup do you think is needed, and how much time will it take? (referring to the overall workload from adapting the project to a specific architecture to achieving full functionality on that architecture). Is this assessment accurate? I look forward to your help and response.

wangyuliu avatar Sep 11 '23 09:09 wangyuliu

In general porting OpenEXR to new platforms is of easy complexity. It already supports a great many architectures, so the bulk of the work will be in determining the new platform's support for 16 bit floats, and a method of performing a cpu id check. If you wish to enable special features of a new platform, that work is of moderate complexity. OpenEXR is already set up to accommodate such special features but it requires attention by the implementor.

meshula avatar Sep 11 '23 16:09 meshula