https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98892
--- Comment #4 from Jim Wilson <wilson at gcc dot gnu.org> --- It turns out that -fmessage-length=0 doesn't work which is odd. I suspect a latent bug in the diagnostic code. I tried -fmessage-length=128, which should work as that is longer than the error line, and does work for this failure, but that causes a different line to fail. Turns out that there is a test that emits a 2.3KB error message. To make the entire testcase work, I need a -fmessage-length value longer than the longest error message, so the smallest power of 2 that works is -fmessage-length=4096 which seems too stupid to submit as a patch.
