https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87209

--- Comment #3 from Martin Sebor <msebor at gcc dot gnu.org> ---
(As suggested in bug 87315) besides issuing a warning it would be safer to do
what Clang does in cases like this and either replace the code with a trap, or
simply eliminate the access (and the malloc call) altogether.

Reply via email to