-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix Invalid Suffix on Literal with PRId in C++11 #63
Conversation
This PR aims to make the C code compilable using nvcc. The cuda language was added as well as a CudaCodePrinter. Changes to stdlib: Wrapped expressions using complex types in an `ifndef __NVCC__` to avoid processing them with the nvcc compiler --------- Co-authored-by: Mouad Elalj, EmilyBourne
This pull request fixes #48, by implementing a tiny wrapper for CUDA and a wrapper for non-CUDA functionalities only with external 'C'. **Commit Summary** - Implemented new header printer for CUDA. - Added CUDA wrapper assignment - Instead of wrapping all local headers, wrap only C functions with extern 'C' --------- Co-authored-by: EmilyBourne <[email protected]> Co-authored-by: bauom <[email protected]>
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 --------- Co-authored-by: EmilyBourne <[email protected]> Co-authored-by: bauom <[email protected]> Co-authored-by: Emily Bourne <[email protected]>
Hello again! Thank you for this new pull request 🤩. Please begin by requesting your checklist using the command |
I can't seem to find your checklist to confirm that you have completed all necessary tasks. Please request one using |
I can't seem to find your checklist to confirm that you have completed all necessary tasks. Please request one using |
Here is your checklist. Please tick items off when you have completed them or determined that they are not necessary for this pull request:
|
/bot run pr_tests |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good job ! Your PR is using all the code it added/changed.
It seems like you have forgotten to complete your checklist for this pull request. Please check the list here, fix the missing items and let me know when everything is ticked and fixed with |
It seems like you have forgotten to complete your checklist for this pull request. Please check the list here, fix the missing items and let me know when everything is ticked and fixed with |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good job ! Your PR is using all the code it added/changed.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good job ! Your PR is using all the code it added/changed.
Unfortunately your PR is not passing the tests so it is not quite ready for review yet. Let me know when it is fixed with |
There are unrecognised tests.
These tests can be run with the command |
/bot run linux |
This pull request addresses issue #59 by adding more CUDA-specific keywords to enhance the checking of variable/function names and prevent name clashes --------- Co-authored-by: EmilyBourne <[email protected]> Co-authored-by: bauom <[email protected]>
This pull request addresses issue #41 by implementing a new feature in Pyccel that allows users to define a custom device **Commit Summary** - Adding handler for custom device and its code generation. - Adding test --------- Co-authored-by: EmilyBourne <[email protected]>
/bot run pr_tests |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good job ! Your PR is using all the code it added/changed.
/bot run pr_tests |
/bot mark as ready |
(PrimitiveIntegerType(),8) : LiteralString("%") + CMacro(' PRId64'), | ||
(PrimitiveIntegerType(),2) : LiteralString("%") + CMacro(' PRId16'), | ||
(PrimitiveIntegerType(),1) : LiteralString("%") + CMacro(' PRId8'), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This seems backwards to me. I would expect
(PrimitiveIntegerType(),8) : LiteralString("%") + CMacro(' PRId64'), | |
(PrimitiveIntegerType(),2) : LiteralString("%") + CMacro(' PRId16'), | |
(PrimitiveIntegerType(),1) : LiteralString("%") + CMacro(' PRId8'), | |
(PrimitiveIntegerType(),8) : LiteralString("% ") + CMacro('PRId64'), | |
(PrimitiveIntegerType(),2) : LiteralString("% ") + CMacro('PRId16'), | |
(PrimitiveIntegerType(),1) : LiteralString("% ") + CMacro('PRId8'), |
as
isn't part of the macro
828d166
to
9234e99
Compare
This pull request addresses issue #62 by adding a space between the % and PRId64/PRId16/PRId8 to fix that.