-
A series of steps to upstream support for CHERI architectures from [tock/tock-cheri](https://github.com/tock/tock-cheri)
- [ ] Replace ubiquitous `usize` with specific sized integers and explicit p…
alevy updated
4 weeks ago
-
Testing the existing CHERI TCs in the latest release had the following issues:
```c
#include
#include
char *buffer = "hello";
int main(int argc, char **argv)
{
char *__capability cap_…
-
Hi. I've been working on rebasing the compiler to LLVM-16. Unfortunately the changes are too big to raise as a PR so @arichardson recommend raising an issue here instead. For testing I've got all the …
-
it would be good to have a quick intro of CHERI including the new state, how it behaves, tagged memory overview etc. so that the reader can get the idea behind CHERI in a few minutes.
-
The purpose of this is not only support the protected mode but also better test bdwgc.
The patches in https://github.com/capablevms/bdwgc (master) should be useful.
Related issue: #461
ivmai updated
1 month ago
-
```
muralivi@muralivi-macbookpro:~/cheriot/cheriot-rtos/examples/error$ cat hello.i
void __attribute__((cheri_compartment(("hello")))) say_hello()
{
xoo::bar();
}
muralivi@muralivi-macbookpro…
-
It's not a great name because it really gates access to all CHERI features - not just registers; you can't use instructions either.
Difficult to think of a really good name - the obvious `CHERI Ena…
-
## Observed Behavior
We see a case that an illegal CHERI LOAD instruction is issued in the pipe, it does not get squashed and is sent for execution to the memory from where it picks up a data v…
-
As mentioned in the meeting yesterday, Microsoft has spent some time considering the composition of CHERI and MTE, specifically as part of our work on CHERI heap temporal safety. Our design is geared…
-
(On second thought, moving this out from #340)
There's a subtle assumption in most CHERI work to date that the address field of a capability is a full machine word and is one half of the CHERI capa…