[docs] pending tasks for contributions updated
@@ -38,17 +38,10 @@ Help us to develop TornadoVM or TornadoVM use cases:
* **TornadoVM use-cases**: Develop use cases that use TornadoVM for acceleration: block-chain, graphical version of NBody, filters for photography, etc.
* **TornadoVM Development / Improvements**: If you would like to contribute to the TornadoVM internals, here is a list of pending tasks/improvements:
-
- - Some unittests expect two devices - if not, an error is produced. Check those unittests and simply ignore the message
- - Some unittests consume a lot of memory (on purpose). Regulate the amount of memory depending on the current target device present in the system.
- - Fix TornadoVM crashes when no OpenCL devices are available - throw an exception instead and inform the user that an OpenCL device is required.
- - Implement deoptimization from parallel OpenCL execution (running the sequential implementation). This should be a fall-back mechanism from GPU/FPGA/multi-core execution.
- Port all Python-2 scripts to Python-3.
- Implement a performance plot suite when running the benchmark runner. This should plot speedups against serial Java as well as stacked bars with breakdown analysis (e.g. time spent on compilation, execution, and data transfers).
- Port TornadoVM to Windows 10 - port bash scripts and adapt Python scripts to build with Windows 10.
-
-
For any other contribution(s), feel free to contact us via Github issues or via email to the following contacts:
Main contacts:
