michaelquellmalz
commented
11 months ago I agree that the porting complexity should be very simple. The NFFT package already works "as is" on the Debian architecture RISCV64 and also the unit tests validate the numerical accuracy of the results on this architecture, see the logs https://buildd.debian.org/status/fetch.php?pkg=nfft&arch=riscv64&ver=3.5.3-1&stamp=1691323460&raw=0
Am 17 Nov 2023 um 09:06 schrieb xuanbao:
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 nfft 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.
— Reply to this email directly, view it on GitHub https://github.com/NFFT/nfft/issues/137, or unsubscribe https://github.com/notifications/unsubscribe-auth/AEHP7F75MHBJEBEG2O7EJ7DYE4LJFAVCNFSM6AAAAAA7PMSNQOVHI2DSMVQWIX3LMV43ASLTON2WKOZRHE4TQNJQG43DGMQ. You are receiving this because you are subscribed to this thread.Message ID: @.***>
--------------ah5KF2xkeShjv4RfxURyrF8w Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: 8bit
I agree that the porting complexity should be very simple. The NFFT package already works "as is" on the Debian architecture RISCV64 and also the unit tests validate the numerical accuracy of the results on this architecture, see the logs https://buildd.debian.org/status/fetch.php?pkg=nfft&arch=riscv64&ver=3.5.3-1&stamp=1691323460&raw=0Hello 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 nfft 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.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.
--------------ah5KF2xkeShjv4RfxURyrF8w--
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 nfft 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.