CHERIoT Platform
What's the status of upstreaming CHERIoT support into LLVM? #469
-
|
Copying discussion from the Signal chat. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
|
The first step before we can upstream is to catch up with where upstream currently is. We started CHERIoT with an LLVM 13 fork. LLVM does a new release roughly every six months and is just about to do the LLVM 20 release (20.1 is the first 20.x release, 20.0 is the unreleased git branch). We just did a CHERIoT LLVM 18 release and are in process of catching up to 19. @resistor has been upstreaming small bits, but we can't start properly until we're tracking upstream. Once we've caught up with the latest release, we'll start doing regular (weekly?) merges and reducing our diff. Our plan after catching up is to cut CHERIoT-LLVM releases alongside the upstream ones until we've managed to upstream everything. And after that, have our tree become a staging area for any new features. We'll probably keep doing releases from our tree, since there will probably continue to be features that we have that aren't yet upstreamed, but we will aim for the RTOS to be buildable with upstream. Upstreaming will also depend on consensus from upstream and on reviewers. |
Beta Was this translation helpful? Give feedback.
The first step before we can upstream is to catch up with where upstream currently is. We started CHERIoT with an LLVM 13 fork. LLVM does a new release roughly every six months and is just about to do the LLVM 20 release (20.1 is the first 20.x release, 20.0 is the unreleased git branch). We just did a CHERIoT LLVM 18 release and are in process of catching up to 19.
@resistor has been upstreaming small bits, but we can't start properly until we're tracking upstream.
Once we've caught up with the latest release, we'll start doing regular (weekly?) merges and reducing our diff.
Our plan after catching up is to cut CHERIoT-LLVM releases alongside the upstream ones until we've managed to upst…