Inconsistent container size selection across equivalent operations

melsonGit / serial_cpp_vs_parallel_cuda

Code work for completion of MSc ICT. The original version of this project was submitted alongside a 15,000 word thesis paper and put into practice the theoretical CPU and GPGPU/GPU elements explored in the write-up. I continued to develop this project post-graduation.

0 stars 1 forks source link

Inconsistent container size selection across equivalent operations #4

Closed melsonGit closed 2 years ago

melsonGit commented 2 years ago

Issue

CPU and GPU operation equivalents don't give users identical container sizes to choose from in e.g. CPU vecAddConSet() and GPU vecAddConSet(). This makes the operation benchmark times inaccurate and beyond comparison.

Additional Info

This issue has only arisen since collating all CPU operations into a single application. CPU and GPU operation equivalents must function under identical container sizes, while also offering identical container sizes to the user.

melsonGit commented 2 years ago

Numerous changes in previous commits focused on this issue. This is now complete.

Closing.