Initial commit: Pyccel Cuda

[EmilyBourne]

The lint error needs fixing (_infere_type->_infer_type was renamed to remove the typo), but from a coverage perspective it is worrying if this difference is not leading to errors

[EmilyBourne]

@EmilyBourne other than the mentions I would like you to take a look on how we implimented the Kernel class and how we handled that. we hacked it in some places like syntactic but i am not sure if that is the only way to do it.

I can't find the Kernel class. Do you mean the KernelCall class?

[EmilyBourne]

As a general remark, why do we use "ccuda" everywhere instead of just "cuda"? The language is cuda. It is c-based, but I don't think there is a "fortrancuda" so I'm not sure where this naming has come from

[EmilyBourne]

/bot trust user bauom

[EmilyBourne]

/bot trust user framdani

[EmilyBourne]

/bot trust user bauom

[github-actions[bot]]

@bauom It looks like the Pyccel maintainers trust you :rocket:. I will now start running tests when you request them.

[EmilyBourne]

/bot trust user framdani

[github-actions[bot]]

@framdani It looks like the Pyccel maintainers trust you :rocket:. I will now start running tests when you request them.

[bauom]

/bot run linux, cuda

[github-actions[bot]]

Ran tests on commit 207cafeed3c2b84122d199217a403331a6df02b7, for more details see here

[bauom]

/bot show tests

[github-actions[bot]]

The following is a list of keywords which can be used to run tests. Tests in bold are run by pull requests 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.
• 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.
• linux_anaconda : Runs the unit tests on a linux system using anaconda for python.
• windows_anaconda : Runs the unit tests on a windows system using anaconda for python.

[EmilyBourne]

@bauom the bot looks for test names separated by spaces linux, will be unknown

[bauom]

/bot run linux cuda

[github-actions[bot]]

Ran tests on commit 207cafeed3c2b84122d199217a403331a6df02b7, for more details see here

• :heavy_check_mark: linux / Unit tests

[EmilyBourne]

/bot run docs

[github-actions[bot]]

Ran tests on commit ff72d7f2268e81ed08a110760745fccc1f8d9d75, for more details see here

• :x: docs / Documentation Format

[EmilyBourne]

/bot run docs

[github-actions[bot]]

Ran tests on commit 91dbd279c47ec746a5b12cafb2ee3d5b3a47a6fa, for more details see here

• :x: docs / Documentation Format