https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95000
--- Comment #2 from felix-gcc at fefe dot de --- The false positive also happens if you fix that. In fact, my original (much longer) code does not try to write to read-only memory. I put that in my test case in the hope that somebody would mention it, so I can point out that gcc -fanalyzer could warn about it, but doesn't. So thank you for falling for my trap. :-)
