public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "xry111 at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/111669] bogus -Wnonnull in conditionally executed code Date: Wed, 04 Oct 2023 01:44:44 +0000 [thread overview] Message-ID: <bug-111669-4-46B66lSkTF@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-111669-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111669 Xi Ruoyao <xry111 at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |xry111 at gcc dot gnu.org --- Comment #1 from Xi Ruoyao <xry111 at gcc dot gnu.org> --- The warning given for the reduced test case is correct because it does not make sense. It should be just rewritten as int GetSystemDirectory16(char *path, int count) { if (GetWindowsDirectoryA()) __builtin_unreachable(); return 0; } because in the case if GetWindowsDirectoryA() returns non-zero, the code always invoke undefined behavior. I'm not sure about the original file.c, but AFAIK GCC developers are keeping to say "hey, don't use -Werror".
next prev parent reply other threads:[~2023-10-04 1:44 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-10-03 4:34 [Bug middle-end/111669] New: " zfigura at codeweavers dot com 2023-10-04 1:44 ` xry111 at gcc dot gnu.org [this message] 2023-10-04 1:46 ` [Bug middle-end/111669] " xry111 at gcc dot gnu.org 2023-10-04 15:44 ` zfigura at codeweavers dot com 2023-10-05 5:42 ` xry111 at gcc dot gnu.org 2023-10-05 5:48 ` xry111 at gcc dot gnu.org 2023-10-05 6:05 ` zfigura at codeweavers dot com 2023-10-05 6:14 ` xry111 at gcc dot gnu.org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-111669-4-46B66lSkTF@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).