Under normal circumstances, doing 8g8 should find the first byte of an invalid UTF-8 sequence, which should be where <e2> is. With Apple clang 16 though, it lands on the next byte, <82> instead. This indicates the compiler miscompiled the code in the UTF-8 handling code.