-
-
Notifications
You must be signed in to change notification settings - Fork 12
Add a post announcing RISC-V support #123
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
Merged
+97
−0
Merged
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
cda59be
Add a post announcing RISC-V support
StanFromIreland 6c40426
Add missing newline at end of file
StanFromIreland 5490060
Apply Hugo's and Ludovic's suggestions
StanFromIreland 15f4f5e
Use Emma's website, and update `publishDate`
StanFromIreland File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
25 changes: 25 additions & 0 deletions
25
content/posts/riscv-now-officially-supported/RISC-V-logo.svg
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,72 @@ | ||
| --- | ||
| title: RISC-V is now officially supported by CPython! | ||
| publishDate: 2026-08-24 | ||
| author: Stan Ulbrych | ||
| description: > | ||
| I’m happy to announce that RISC-V platforms are now officially supported by | ||
| CPython. 🎉 🚀 | ||
| tags: [] | ||
| published: true | ||
| --- | ||
| Over the last few months, I’ve been working on improving CPython’s support for | ||
| the RISC-V architecture, and I’m thrilled to announce that RISC-V is now | ||
| officially supported by CPython as a [tier 3](https://peps.python.org/pep-0011/#tier-3) | ||
| platform! 🎉 🚀 | ||
|
|
||
| ## What is RISC-V? | ||
|
|
||
|  | ||
|
|
||
| [RISC-V](https://riscv.org/) is an open [instruction set architecture (ISA)](https://en.wikipedia.org/wiki/Instruction_set_architecture). Importantly, | ||
| unlike proprietary instruction sets (such as x86 and ARM), it is developed as an | ||
| open standard and can be implemented by anyone. | ||
|
|
||
| Its ecosystem has grown considerably in recent years and is [projected to | ||
| quadruple by 2032](https://finance.yahoo.com/technology/articles/risc-v-market-projected-quadruple-101200888.html). With that growth, it’s increasingly important that | ||
| Python works reliably on these platforms. | ||
|
|
||
| ## Getting here | ||
|
|
||
| This would not have been possible without community contributions. RISC-V support | ||
| in CPython has developed over time with people testing on real hardware, | ||
| fixing architecture-specific issues, improving build support, reporting bugs, | ||
| and reviewing patches. That work is what has brought the platform to the point | ||
| where it could be added to [PEP 11](https://peps.python.org/pep-0011/). | ||
|
|
||
|  | ||
|
|
||
| A particularly important part of this has been having reliable, ongoing testing | ||
| on real RISC-V hardware. I’d like to thank the [RISE Project](https://riseproject.dev/) for their | ||
| support. RISE has kindly provided several RISC-V machines for CPython, | ||
| giving us buildbots for testing as well as debugging architecture-specific issues. | ||
|
|
||
| I’d especially like to thank [Ludovic Henry](https://github.com/luhenry) from the RISE Project, | ||
| [Furkan Onder](https://github.com/furkanonder), and [Emma Smith](https://emmatyping.dev/), along with the many others who have | ||
| contributed. Additionally, I'm personally grateful for the [Sovereign Tech Agency](https://www.sovereign.tech/), | ||
| which through their amazing fellowship supported my work on this. | ||
|
|
||
| ## What’s next? | ||
|
|
||
| While tier 3 support is an important milestone, there’s plenty more to do. | ||
| We are currently investigating how to improve our testing further by bringing | ||
| RISC-V directly into CPython’s CI, again kindly supported by RISE with their | ||
| [RISE RISC-V Runners initiative](https://riscv-runners.riseproject.dev/). This should give contributors faster | ||
| feedback than the [buildbots](https://buildbot.python.org/) (which usually run *after* a patch is merged) | ||
| and would allow us to catch RISC-V-specific problems earlier. | ||
|
|
||
| In the long term, I’d also love to work towards promoting RISC-V to tier 2 support. | ||
|
|
||
| There are also opportunities to move beyond simply making CPython work on RISC-V. | ||
|
StanFromIreland marked this conversation as resolved.
|
||
| I’d like to explore architecture-specific optimizations to take better advantage | ||
| of RISC-V capabilities where doing so can improve CPython’s performance. | ||
|
|
||
| Importantly, we need people to use it and give us feedback. If you have access | ||
| to RISC-V hardware, please try building and running CPython, run your workloads | ||
| and test suites, and please [let us know what breaks](https://github.com/python/cpython/issues). Testing across | ||
| different RISC-V environments will help us make support better for everyone! | ||
|
|
||
| CPython is also only one part of the Python ecosystem. Continued community work | ||
| across packages, compilers, tooling, and infrastructure will be important in | ||
| making RISC-V an increasingly well-supported platform for Python as a whole. | ||
|
|
||
| There’s a lot still to do, and I’m looking forward to continuing that work! | ||
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.