-fcatch-undefined-behavior false positive with

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

that is kind of awesome. Though, Richard, what're the thoughts on
fail-and-continue (unaligned reads in this case don't fail on this
platform do they? They're just possibly slower? (of course compilers
could still exploit this at some point, but the point of
-fcatch-undefined-behavior is to help us fix the issues before we
exploit those features (or after as a sanity check that the program was
already broken))) ot possible blacklists of known errors? Or both? Fail
and continue and log all the errors in order, suppress things in the
blacklist and then walk through the rest, fixing as many as possible
before iterating again for the next set of failures?