Robert Clausecker

@VadimKulagin Could you reopen this one? The problem is that `UNSERIALIZABLE_OBJECT_MAX_LEN` overflows a 32 bit integer, which is the size of an `int` on 32 bit platforms.

@davidchisnall I do not know if it is supported for booting.

If you do so, please bump directly to v0.5.0 to fix the build on riscv64, too.

Ran into the same issue today: I distribute packages from my 13.2-based host, while building them on/for a 14.0 box. For security, packages are signed on the 13.2-based host, which...

Unfortunately, I have no idea what the problem is. There is going to be a new libfreefare release soonish which is going to fix many of these issues. I hope...

The `volatile` qualifier does not imply atomicity constraints and does not imply any special memory ordering constraints. Its purpose is to model memory-mapped peripherals or other to be a debug...

@trolando I don't see how `must_suspend` is a non-atomic access. You are writing to the variable from one thread and read it concurrently from another. An atomic variable is required...

> So far I can partially modify Lace to use atomics instead of volatile variables, but I find that the generated code is less optimized. For example, Lace has a...

Why don't you do any error checking, especially with the type assertions? Please make sure that all type assertions are successful. In the meanwhile, let me check what went wrong....

It seems like I get a NULL pointer somewhere. I should definitely check for that in case someone forgets to check for errors.