@dr2chase @marcan@treehouse.systems it is possible to build that specific part of the code with -O0 too, or to be even more verbose use
```
__attribute__((optimize(0)))
```
around the functions where the bad behaviour happens.

it is not a gcc12 specific issue by the way, for a few other cases I needed to do something similar in ARM builds.