Richard Brooksby

So now `gcc -ffreestanding -nostdlib -DCONFIG_PLINTH_NONE -DCONFIG_PF_ANSI --entry mps_lib_assert_fail mps.c mpslibfs.c vmfs.c` on Ubuntu 22 says: ``` /usr/bin/ld: /tmp/cct0FyDm.o: in function `mps_arena_release': mps.c:(.text+0x525): undefined reference to `_setjmp' /usr/bin/ld: /tmp/cct0FyDm.o: in...

Assigned priority "optional" since it seems very likely that the MPS core is still freestanding from the above. But it would still be good to have a CI test for...

Revisit this when #38 is resolved. That will probably eliminate the dependencies on `setjmp` so that the build commands above succeed. Then we can add a simple CI check script.

The index to source code will need updating (see also #153 ) and the manual for the new preprocessor symbols.

> It may well be worth doing a quick `Dockerfile` ... One of the things I'm not clear about is whether we can be sure that tests run inside containers,...

> #145 also relevant, since Cirrus CI seems to be mostly layered on Docker. See "is this really LI?" in https://github.com/Ravenbrook/mps/blob/0442b6089ddd0aa33d5bb0de3f620a958d4b33c6/.cirrus.yml#L82-L92

> This is a more interesting build error Are you not getting a 64-bit `unsigned long long`? https://github.com/Ravenbrook/mps/blob/142999bd7b0d265ea793817d662047953e4e13ab/code/clock.h#L111

Ah yes. Looks like a 64-bit assumption has crept in here https://github.com/Ravenbrook/mps/blob/142999bd7b0d265ea793817d662047953e4e13ab/code/clock.h#L156-L162 but since https://github.com/Ravenbrook/mps/blob/142999bd7b0d265ea793817d662047953e4e13ab/code/mps.h#L77 we could switch here on `MPS_WORD_WIDTH` or define `MPS_CLOCK_WIDTH` to be `MPS_WORD_WIDTH` and switch on...

`EVENT_CLOCK_MAKE` is only used in https://github.com/Ravenbrook/mps/blob/142999bd7b0d265ea793817d662047953e4e13ab/code/eventtxt.c#L152-L166 which is intended to only be run on the same platform as the MPS that generated the telemetry, though we might be able to...

Executing [proc.review.edit](https://github.com/Ravenbrook/mps/blob/branch/2023-01-19/review-procedure/procedure/review.rst#57-review-edit) on #34 1. Start time 07:00 2. Improving the design documentation requires a fairly deep dive into the original use case, and this took a while, so not...