https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85777
--- Comment #16 from Vincent Lefèvre <vincent-gcc at vinc17 dot net> --- Well, concerning the initial testcase (and its cleaned-up version), the issue is either fixed or hidden by another bug, which I've just reported: PR99944. Indeed, I now get a maybe-uninitialized warning, but on f (which is incorrect) instead of f[0]. Concerning the other testcase from Comment 14, I was wrong: -fsanitize=undefined actually has the opposite effect, so that this is a different bug, which I've reported: PR99945.
