Improve reliability of the Callback implementation #755
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
These changes are made since some combinations of code and compiler versions sometimes lead to erroneous machine code being generated, because of the somewhat adventurous implementation in Callback.h. The first change prevents the GCC compiler from applying optimizations that assume the code follows strict aliasing rules. The second one prevents the GCC compiler from sometimes generating incorrect inline code for the Callback constructor. The machine code generated with these changes are, on the one hand, less optimal. But on the other hand, the changes should prevent bugs arising from undefined behavior that is tricky to find in the Callback implementation, or simply from compiler bugs in GCC. The philosophy here is that it's better to be safe than sorry, rather than trying to find and fix every single dangerous construct in the code.
See also this post from a few years ago by one of the authors of Callback.h: https://answers.launchpad.net/gcc-arm-embedded/+question/686870