Follow-up Comment #2, bug #60798 (project make): I couldn't find any signs of GCC becoming clever enough to detect why this code is correct. Minor code changes can silence the _stringop-overflow_ warnings.
The next warning I get (GCC11) is a _return-local-addr_ warning in src/read.c:2534 (find_percent_cached). Maybe GCC doesn't recognize alloca as a heap allocation? Just guessing; this warning was not obvious to me. (file #52420) _______________________________________________________ Additional Item Attachment: File name: SV-60798-Silence-bogus-GCC10-stringop-overflow-warni.patch Size:2 KB <https://file.savannah.gnu.org/file/SV-60798-Silence-bogus-GCC10-stringop-overflow-warni.patch?file_id=52420> _______________________________________________________ Reply to this item at: <https://savannah.gnu.org/bugs/?60798> _______________________________________________ Message sent via Savannah https://savannah.gnu.org/