https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95000
--- Comment #7 from CVS Commits ---
The master branch has been updated by David Malcolm :
https://gcc.gnu.org/g:d1d95846e3c901faea6fe36a36e47b9169f5b133
commit r12-7659-gd1d95846e3c901faea6fe36a36e47b9169f5b133
Author: David Malcolm
Date: Tu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95000
David Malcolm changed:
What|Removed |Added
Depends on||104940
--- Comment #6 from David Malcolm
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95000
--- Comment #5 from Dmitry G. Dyachenko ---
gcc version 11.0.0 20210210 (experimental) [master revision
bd0e37f68a3:deed5164277:72932511053596091ad291539022b51d9f2ba418]
PASS for me
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95000
David Malcolm changed:
What|Removed |Added
Ever confirmed|0 |1
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95000
--- Comment #3 from David Malcolm ---
Thanks for filing this bug.
I've filed PR analyzer/95007 to track the RFE for a warning about writes to a
string literal.
Clearly there's a bug somewhere in the handling for the path condition for the
warni
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 mentio
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95000
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
--- Comment #1
