Add support for kernels

[smazouz42]

This pull request addresses issue #28 by implementing a new feature in Pyccel that allows users to define custom GPU kernels. The syntax for creating these kernels is inspired by Numba. and I also need to fix issue #45 for testing purposes

Commit Summary

• Introduced KernelCall class
• Added cuda printer methods _print_KernelCall and _print_FunctionDef to generate the corresponding CUDA representation for both kernel calls and definitions
• Added IndexedFunctionCall represents an indexed function call
• Added CUDA module and cuda.synchronize()
• Fixing a bug that I found in the header: it does not import the necessary header for the used function

[pyccel-bot[bot]]

Hello! Welcome to Pyccel! Thank you very much for your contribution :heart:.

I am the GitHub bot. I will help guide you through the different stages necessary to validate a review in Pyccel. If you haven't yet seen our developer docs make sure you check them out here. Amongst other things they describe the review process that we have just started. You can also get in touch with our other developers on our Pyccel Discord Server.

To begin with I will give you a short checklist to make sure your pull request is complete. Please tick items off when you have completed them or determined that they are not necessary for this pull request. If you want me to run any specific tests to check out corner cases that you can't easily check on your computer, you can request this using the command /bot run X. Use the command /bot show tests to see a full list of the tests I can run. Once you have finished preparing your pull request and are ready to request reviews just take your PR out of draft, or let me know with the command /bot mark as ready. I will then run the full suite of tests to check that everything is as neat as you think before asking other contributors for reviews. Tests will not run automatically before this point to avoid wasting resources. You can get a full list of commands that I understand using /bot commands.

Please begin by requesting your checklist using the command /bot checklist

[smazouz42]

Here is your checklist. Please tick items off when you have completed them or determined that they are not necessary for this pull request:

• [x] Write a clear PR description
• [x] Add tests to check your code works as expected
• [x] Update documentation if necessary
• [x] Update Changelog
• [x] Ensure any relevant issues are linked
• [x] Ensure new tests are passing

[smazouz42]

/bot run cuda

[smazouz42]

/bot

[smazouz42]

/bot show tests

[pyccel-bot[bot]]

The following is a list of keywords which can be used to run tests. Tests in bold are run by pull requests when they are marked as ready for review:

• linux : Runs the unit tests on a Linux system.
• windows : Runs the unit tests on a Windows system.
• macosx : Runs the unit tests on a MacOS X system.
• cuda : Runs the cuda unit tests on a Linux system.
• coverage : Runs the unit tests on a Linux system and checks the coverage of the tests.
• docs : Checks if the documentation follows the numpydoc format.
• pylint : Runs pylint on files which are too big to be handled by codacy.
• pyccel_lint : Runs a linter to check that Pyccel's best practices are followed.
• spelling : Checks if everything in the documentation is spelled (and capitalised) correctly.
• pr_tests : Runs all the tests marked in bold.
• pickle : Checks that .pyccel files have been correctly generated and installed by the installation process.
• editable_pickle : Checks that .pyccel files have been correctly generated and installed by the editable installation process.
• pickle_wheel : Checks that .pyccel files have been correctly generated and packaged into the wheel.
• anaconda_linux : Runs the unit tests on a linux system using anaconda for python.
• anaconda_windows : Runs the unit tests on a windows system using anaconda for python.
• intel : Runs the unit tests on a linux system using the intel compiler.

These tests can be run with the command /bot run X (multiple tests can be specified separated by spaces), or with try V X to test on Python version V.

[smazouz42]

/bot run docs pylint spelling pyccel_lint

[smazouz42]

/bot run docs pylint spelling pyccel_lint

[smazouz42]

/bot run docs pylint spelling pyccel_lint

[smazouz42]

/bot run docs pylint spelling pyccel_lint

[smazouz42]

/bot run docs pylint spelling pyccel_lint

[smazouz42]

/bot run docs

[smazouz42]

/bot run docs

[smazouz42]

/bot run docs pylint spelling pyccel_lint

[smazouz42]

/bot run docs pylint spelling pyccel_lint

[smazouz42]

/bot run docs pylint

[smazouz42]

/bot run docs pylint

[smazouz42]

/bot run docs

[smazouz42]

/bot run docs

[smazouz42]

/bot run docs pylint spelling pyccel_lint

[smazouz42]

/bot

[smazouz42]

/bot run linux

[pyccel-bot[bot]]

This bot reacts to all comments which begin with /bot. This phrase can be followed by any of these commands:

• show tests : Lists the tests which can be triggered
• run X : Triggers the test X (acceptable values for X can be seen using show tests). Multiple tests can be specified separated by spaces.
• try V X : Triggers the test X (acceptable values for X can be seen using show tests) using Python version V. Multiple tests can be specified separated by spaces, but all will use the same Python version.
• mark as ready : Runs the PR tests. If they pass then it adds the appropriate review flag and requests reviews. This command should be used when the PR is first ready for review, or when a review has been answered.
• commands : Shows this list detailing all the commands which are understood.
• trust user X : Tells the bot that a new user X is trusted to run workflows (prevents misuse of GitHub actions for mining etc). This command can only be used by a trusted reviewer.

Beware: if you have never contributed to this repository and you are not a member of the Pyccel organisation, the bot will ignore all requests to run tests until permitted by a trusted reviewer.

[smazouz42]

/bot run macosx windows

[pyccel-bot[bot]]

I can't seem to find your checklist to confirm that you have completed all necessary tasks. Please request one using /bot checklist.

[smazouz42]

/bot show tests

[pyccel-bot[bot]]

The following is a list of keywords which can be used to run tests. Tests in bold are run by pull requests when they are marked as ready for review:

• linux : Runs the unit tests on a Linux system.
• windows : Runs the unit tests on a Windows system.
• macosx : Runs the unit tests on a MacOS X system.
• cuda : Runs the cuda unit tests on a Linux system.
• coverage : Runs the unit tests on a Linux system and checks the coverage of the tests.
• docs : Checks if the documentation follows the numpydoc format.
• pylint : Runs pylint on files which are too big to be handled by codacy.
• pyccel_lint : Runs a linter to check that Pyccel's best practices are followed.
• spelling : Checks if everything in the documentation is spelled (and capitalised) correctly.
• pr_tests : Runs all the tests marked in bold.
• pickle : Checks that .pyccel files have been correctly generated and installed by the installation process.
• editable_pickle : Checks that .pyccel files have been correctly generated and installed by the editable installation process.
• pickle_wheel : Checks that .pyccel files have been correctly generated and packaged into the wheel.
• anaconda_linux : Runs the unit tests on a linux system using anaconda for python.
• anaconda_windows : Runs the unit tests on a windows system using anaconda for python.
• intel : Runs the unit tests on a linux system using the intel compiler.

These tests can be run with the command /bot run X (multiple tests can be specified separated by spaces), or with try V X to test on Python version V.

[smazouz42]

/bot run cuda

[smazouz42]

/bot run pr_tests

[smazouz42]

/bot run checklist

[pyccel-bot[bot]]

There are unrecognised tests. The following is a list of keywords which can be used to run tests. Tests in bold are run by pull requests when they are marked as ready for review:

• linux : Runs the unit tests on a Linux system.
• windows : Runs the unit tests on a Windows system.
• macosx : Runs the unit tests on a MacOS X system.
• cuda : Runs the cuda unit tests on a Linux system.
• coverage : Runs the unit tests on a Linux system and checks the coverage of the tests.
• docs : Checks if the documentation follows the numpydoc format.
• pylint : Runs pylint on files which are too big to be handled by codacy.
• pyccel_lint : Runs a linter to check that Pyccel's best practices are followed.
• spelling : Checks if everything in the documentation is spelled (and capitalised) correctly.
• pr_tests : Runs all the tests marked in bold.
• pickle : Checks that .pyccel files have been correctly generated and installed by the installation process.
• editable_pickle : Checks that .pyccel files have been correctly generated and installed by the editable installation process.
• pickle_wheel : Checks that .pyccel files have been correctly generated and packaged into the wheel.
• anaconda_linux : Runs the unit tests on a linux system using anaconda for python.
• anaconda_windows : Runs the unit tests on a windows system using anaconda for python.
• intel : Runs the unit tests on a linux system using the intel compiler.

These tests can be run with the command /bot run X (multiple tests can be specified separated by spaces), or with try V X to test on Python version V.

[smazouz42]

/bot run pr_tests

[smazouz42]

/bot run cuda

[smazouz42]

/bot run cuda

[smazouz42]

/bot run cuda

[smazouz42]

/bot run cuda

[smazouz42]

/bot run cuda

[smazouz42]

/bot run pr_tests

[smazouz42]

/bot run pr_tests

[smazouz42]

/bot run linux

[smazouz42]

/bot run linux

[smazouz42]

/bot run pr_tests

[smazouz42]

/bot run pr_tests

[smazouz42]

/bot run pr_tests

[smazouz42]

/bot run pr_tests

[smazouz42]

/bot run cuda

[smazouz42]

/bot run pr_tests

[smazouz42]

/bot run cuda

[smazouz42]

/bot run cuda

[smazouz42]

/bot run pr_tests