AcademySoftwareFoundation / AcademySoftwareFoundation/openexr
Assessment of the difficulty in porting CPU architecture for openexr
- Dominant language
- C
- Stars
- 1.8k
- Forks
- 700
- Avg merge
- 3d 12h
- Merged PRs (30d)
- 29
Description
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.
Contributor guide
Research direction
No files, tests, or entry points are identified. Start by reviewing the stated scanning-tool assessment and the scope of adapting OpenEXR to a specific CPU architecture. Done would be a documented, community-supported estimate of the required team configuration, workload, and time.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- operating-systems
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100