Guillaume E

> The references to the kernel are to provide access to the list of processes that all of those types need in some way. AppId, in particular, is shared with...

> If the Tock kernel does not run code in interrupt context, and will remain single-threaded, then we could use normal (non-`mut`) `static` declarations as well. I think a `TockStatic`...

Thanks for the explanation on how interrupts are handled! Much clearer indeed.

Nice find @bradjc! We still need to extract the main Makefile's directory instead of hard-coding a given user's build directory.

Updated the list to refer to #1657, as the Makefile doesn't seem idempotent.

> #1657 was merged, has this been addressed at this point? I can check the box, although the reason is still unclear, so it might come back when we update...

I did a quick test, building the imix board in two build folders (`/path/to/tock` and `/path/to/tock2`) on the same machine. The SHA-256 were different. Using `V=1 make` in the `boards/imix/`...

Following https://github.com/rust-secure-code/wg/issues/28#issuecomment-455734921, I also tried to use `--remap-path-prefix` for `$HOME` (but this overrode the current `--remap-path-prefix`), as well as `$HOME/.cargo` and `$HOME/.rustup` (these two had no effect on the SHA-256)....

I did a few more tests. - If I copy the `boards/imix` folder into `boards/imix2`, both build the same binary. - If I copy the `boards/components` folder into `boards/components2`, and...

With #1714 (currently in review), we're getting close to having reproducible builds of Tock! One remaining discrepancy is due to the `TOCK_KERNEL_VERSION` value embedded in some panic messages, because this...