Skip to content
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

Updated CUDA Name Clash Checker By Added CUDA-specific keywords #60

Merged
merged 19 commits into from
Jul 3, 2024

Conversation

smazouz42
Copy link

This pull request addresses issue #59 by adding more CUDA-specific keywords to enhance the checking of variable/function names and prevent name clashes

EmilyBourne and others added 6 commits June 11, 2024 17:04
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]>
@pyccel-bot
Copy link

pyccel-bot bot commented Jun 26, 2024

Hello again! Thank you for this new pull request 🤩.

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

@smazouz42 smazouz42 self-assigned this Jun 26, 2024
@github-actions github-actions bot marked this pull request as draft June 26, 2024 20:02
@smazouz42 smazouz42 linked an issue Jun 26, 2024 that may be closed by this pull request
@smazouz42
Copy link
Author

smazouz42 commented Jun 26, 2024

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

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

@smazouz42 smazouz42 marked this pull request as ready for review June 26, 2024 20:05
@github-actions github-actions bot marked this pull request as draft June 26, 2024 20:07
@pyccel-bot
Copy link

pyccel-bot bot commented Jun 26, 2024

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 /bot mark as ready.

@smazouz42 smazouz42 marked this pull request as ready for review June 27, 2024 10:39
@github-actions github-actions bot marked this pull request as draft June 27, 2024 10:40
@pyccel-bot
Copy link

pyccel-bot bot commented Jun 27, 2024

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 /bot mark as ready.

@smazouz42 smazouz42 marked this pull request as ready for review June 27, 2024 10:44
@github-actions github-actions bot marked this pull request as draft June 27, 2024 10:45
@pyccel-bot
Copy link

pyccel-bot bot commented Jun 27, 2024

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 /bot mark as ready.

Copy link

@pyccel-bot pyccel-bot bot left a 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.

Copy link

@pyccel-bot pyccel-bot bot left a 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.

@smazouz42
Copy link
Author

/bot run docs

@pyccel-bot
Copy link

pyccel-bot bot commented Jul 2, 2024

@smazouz42, @EmilyBourne has a few questions/comments about your code. Can you go through and see if you agree with them. If not go ahead and explain why. Once you've adressed all the comments let me know with /bot mark as ready and we will see if we can get approval.

@pyccel-bot pyccel-bot bot removed the Ready_for_review Received at least one approval. Requires review from senior developer label Jul 2, 2024
@smazouz42
Copy link
Author

/bot run pr_tests

Copy link

@pyccel-bot pyccel-bot bot left a 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.

@EmilyBourne EmilyBourne marked this pull request as ready for review July 2, 2024 21:16
@pyccel-bot pyccel-bot bot added the Ready_to_merge Approved by senior developer. Ready for final approval and merge label Jul 2, 2024
Copy link

@pyccel-bot pyccel-bot bot left a 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.

@pyccel-bot pyccel-bot bot added Ready_to_merge Approved by senior developer. Ready for final approval and merge and removed Ready_to_merge Approved by senior developer. Ready for final approval and merge labels Jul 2, 2024
@EmilyBourne EmilyBourne enabled auto-merge (squash) July 2, 2024 21:18
@github-actions github-actions bot marked this pull request as draft July 2, 2024 21:33
auto-merge was automatically disabled July 2, 2024 21:33

Pull request was converted to draft

@pyccel-bot pyccel-bot bot removed the Ready_to_merge Approved by senior developer. Ready for final approval and merge label Jul 2, 2024
@smazouz42 smazouz42 marked this pull request as ready for review July 3, 2024 10:49
Copy link

@pyccel-bot pyccel-bot bot left a 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.

@pyccel-bot pyccel-bot bot added the Ready_to_merge Approved by senior developer. Ready for final approval and merge label Jul 3, 2024
@EmilyBourne EmilyBourne enabled auto-merge (squash) July 3, 2024 16:35
@EmilyBourne EmilyBourne merged commit 96fdbb3 into devel Jul 3, 2024
23 of 24 checks passed
@EmilyBourne EmilyBourne deleted the issues/59 branch July 3, 2024 16:37
EmilyBourne added a commit that referenced this pull request Jul 11, 2024
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]>
EmilyBourne added a commit that referenced this pull request Jul 15, 2024
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]>
EmilyBourne added a commit that referenced this pull request Jul 17, 2024
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]>
EmilyBourne added a commit that referenced this pull request Jul 19, 2024
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]>
EmilyBourne added a commit that referenced this pull request Jul 26, 2024
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]>
EmilyBourne added a commit that referenced this pull request Aug 29, 2024
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]>
EmilyBourne added a commit that referenced this pull request Sep 3, 2024
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]>
EmilyBourne added a commit that referenced this pull request Sep 25, 2024
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]>
EmilyBourne added a commit that referenced this pull request Nov 8, 2024
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]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Ready_to_merge Approved by senior developer. Ready for final approval and merge
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Advanced CUDA Name Clash Checker
4 participants