Skip to content

Conversation

davy39
Copy link
Contributor

@davy39 davy39 commented Sep 25, 2025

Description

Add a new Clang C23 kernel, for those who need to code in C and not with C++ (lot of students in France).

Edit : + c11 & c17

Type of change

Please tick all options which are relevant.

  • Bug fix
  • New feature
  • Added/removed dependencies
  • Required documentation updates

@anutosh491
Copy link
Collaborator

Thanks for opening this. Saying this cause I've gotten multiple messages on mail and LinkedIn for a C kernel (yes only C and not c++)

@codecov-commenter
Copy link

codecov-commenter commented Sep 25, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 81.78%. Comparing base (81fed93) to head (bc0c694).

Additional details and impacted files

Impacted file tree graph

@@           Coverage Diff           @@
##             main     #379   +/-   ##
=======================================
  Coverage   81.78%   81.78%           
=======================================
  Files          20       20           
  Lines         950      950           
  Branches       87       87           
=======================================
  Hits          777      777           
  Misses        173      173           
🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@mcbarton
Copy link
Collaborator

Feels like since we have a c++17 kernel, then it might make sense to add a c17 standard kernel as well, but this is just my opinion.

@vgvassilev
Copy link
Contributor

@davy39, thanks for your pull request. Do you think you can add kernels for the other standard c versions, too?

@davy39
Copy link
Contributor Author

davy39 commented Sep 25, 2025

Now my PR include c11, c17 and c23.

@vgvassilev
Copy link
Contributor

Now my PR include c11, c17 and c23.

Thank you! @mcbarton do you know why the docs build fails?

@mcbarton
Copy link
Collaborator

mcbarton commented Sep 26, 2025

Now my PR include c11, c17 and c23.

Thank you! @mcbarton do you know why the docs build fails?

@vgvassilev Honestly I have no idea. It looks like a random failure. It doesn't appear to be anything to do with main as I rebased the sub interpreter PR #380 to check and it built the read the docs. My suggestion is for @davy39 to either squash his 2 commits and repush, or push an empty commit to rerun the read the docs workflow.

@mcbarton
Copy link
Collaborator

This appears to be passing the read the docs workflow now. I will take this in once the ci goes green.

@davy39
Copy link
Contributor Author

davy39 commented Sep 26, 2025

Sorry for messing up with git... I had to force-push few times to get what I wanted :)

@mcbarton mcbarton merged commit 4449bfb into compiler-research:main Sep 26, 2025
26 of 27 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants