public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dmalcolm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug analyzer/108733] New: -Wanalyzer-use-of-uninitialized-value false positives seen with __attribute__((cleanup)) Date: Wed, 08 Feb 2023 23:42:21 +0000 [thread overview] Message-ID: <bug-108733-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108733 Bug ID: 108733 Summary: -Wanalyzer-use-of-uninitialized-value false positives seen with __attribute__((cleanup)) Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: analyzer Assignee: dmalcolm at gcc dot gnu.org Reporter: dmalcolm at gcc dot gnu.org Target Milestone: --- Created attachment 54439 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=54439&action=edit Reproducer Am seeing various false positives in qemu from -Wanalyzer-use-of-uninitialized-value with __attribute__((cleanup)) Seems to happen at -O1 and above with the attached reproducer, with both trunk and gcc 12.2: Trunk: https://godbolt.org/z/GdrY49151 12.2: https://godbolt.org/z/rjzvjd3qG In function 'g_autoptr_cleanup_generic_gfree', inlined from 'spapr_cap_get_string' at <source>:60:67: <source>:15:3: warning: use of uninitialized value '*(void **)&val' [CWE-457] [-Wanalyzer-use-of-uninitialized-value] 15 | g_free(*pp); | ^~~~~~~~~~~ 'spapr_cap_get_string': events 1-4 | | 60 | __attribute__((cleanup(g_autoptr_cleanup_generic_gfree))) char* val = NULL; | | ^~~ | | | | | (1) region created on stack here | | (4) inlined call to 'g_autoptr_cleanup_generic_gfree' from 'spapr_cap_get_string' |...... | 63 | if (value >= cap->possible->num) { | | ~ | | | | | (2) following 'true' branch... | 64 | error_setg_internal((errp), | | ~~~~~~~~~~~~~~~~~~~ | | | | | (3) ...to here | +--> 'g_autoptr_cleanup_generic_gfree': event 5 | | 15 | g_free(*pp); | | ^~~~~~~~~~~ | | | | | (5) use of uninitialized value '*(void **)&val' here | Compiler returned: 0
next reply other threads:[~2023-02-08 23:42 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-02-08 23:42 dmalcolm at gcc dot gnu.org [this message] 2023-02-09 22:11 ` [Bug analyzer/108733] " cvs-commit at gcc dot gnu.org 2023-02-09 22:18 ` dmalcolm at gcc dot gnu.org 2023-03-29 18:19 ` cvs-commit at gcc dot gnu.org 2023-03-29 19:31 ` dmalcolm 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-108733-4@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).