https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94774
--- Comment #1 from Martin Sebor <msebor at gcc dot gnu.org> --- It looks to me like only the second warning might be a true positive. The first one seems spurious since the uninitialized access is guarded by the test for safe being true. Moving the guard up would suppress the dump output in the "unsafe" case so I don't think that's what we want. OTOH, ether initializing the array, or unconditionally assigning to it in is_call_safe, seems benign.
