Consider the following statement:
> On a platform that has well-defined signed overflow, it's not a bug to perform signed overflow.
If you've ever cranked up GCC's optimization settings on a program that performs signed overflow, you know this simply isn't true.
In general, the fact that the underlying hardware supports a certain set of machine semantics does not guarantee that the implementation will extend the semantics of the C or C++ abstract machine to match. It of course may do so—after all, it may do whatever it pleases once your program exhibits undefined behaviour—but unless you are specifically targeting your implementation's C- or C++-like dialect instead of ISO C or C++, accessing unaligned memory is a bug.
> Ubsan should adopt a couple of other safety improvements from C++
I agree that these should be adopted, but disagree that it should be ubsan which does so. These are statically detectable errors, so it should be the compiler which implements the detection, be it as a QOI extension or as part of the language standard.