public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "kdudka at redhat dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug analyzer/104308] no location info provided for [-Wanalyzer-use-of-uninitialized-value] warnings Date: Wed, 13 Apr 2022 07:51:55 +0000 [thread overview] Message-ID: <bug-104308-4-nUJyzmrMQZ@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-104308-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104308 Kamil Dudka <kdudka at redhat dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|FIXED |--- Status|RESOLVED |ASSIGNED --- Comment #8 from Kamil Dudka <kdudka at redhat dot com> --- As spotted by Vincent Mihalkovic, the fix seems to be incomplete. If we run gcc-12.0.1-0.14.fc37.x86_64 on the following test-case, some diagnostic messages are still printed without any location info: $ cat test-memcpy.c #include <string.h> int main(void) { char a1[5]; char a2[5]; return (memcpy(a1, a2, 5) == a1); } $ gcc -fanalyzer -fdiagnostics-path-format=separate-events -c test-memcpy.c In function ‘main’: cc1: warning: use of uninitialized value ‘*(unsigned char (*)[5])(&a2[0])’ [CWE-457] [-Wanalyzer-use-of-uninitialized-value] test-memcpy.c:6:10: note: (1) region created on stack here 6 | char a2[5]; | ^~ cc1: note: (2) use of uninitialized value ‘*(unsigned char (*)[5])(&a2[0])’ here
next prev parent reply other threads:[~2022-04-13 7:51 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-01-31 15:09 [Bug analyzer/104308] New: " kdudka at redhat dot com 2022-01-31 15:56 ` [Bug analyzer/104308] " dmalcolm at gcc dot gnu.org 2022-01-31 15:57 ` dmalcolm at gcc dot gnu.org 2022-01-31 16:40 ` kdudka at redhat dot com 2022-01-31 16:50 ` dmalcolm at gcc dot gnu.org 2022-03-25 21:52 ` dmalcolm at gcc dot gnu.org 2022-03-25 21:52 ` dmalcolm at gcc dot gnu.org 2022-03-28 13:44 ` cvs-commit at gcc dot gnu.org 2022-03-28 13:52 ` dmalcolm at gcc dot gnu.org 2022-04-13 7:51 ` kdudka at redhat dot com [this message] 2022-04-13 22:05 ` dmalcolm at gcc dot gnu.org 2022-04-14 13:27 ` dmalcolm at gcc dot gnu.org 2022-04-25 23:36 ` cvs-commit at gcc dot gnu.org 2022-04-25 23:39 ` 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-104308-4-nUJyzmrMQZ@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).