public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dcb314 at hotmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug analyzer/98564] New: valgrind error with -fanalyzer Date: Wed, 06 Jan 2021 14:55:07 +0000 [thread overview] Message-ID: <bug-98564-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98564 Bug ID: 98564 Summary: valgrind error with -fanalyzer Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: analyzer Assignee: dmalcolm at gcc dot gnu.org Reporter: dcb314 at hotmail dot com Target Milestone: --- For this one line of C source code: void a(void) { int b = calloc(0, 1); } compiled by recent gcc trunk, built with valgrind, does this: $ /home/dcb/gcc/results.20210105.valgrind/bin/gcc -fanalyzer -c -w bug687.c ==65008== Conditional jump or move depends on uninitialised value(s) ==65008== at 0xF7DD7F: ana::exploded_path::feasible_p(ana::logger*, ana::feas ibility_problem**, ana::engine*, ana::exploded_graph const*) const (engine.cc:34 84) ==65008== by 0x1733AA4: ana::dedupe_winners::add(ana::logger*, shortest_paths <ana::eg_traits, ana::exploded_path> const&, ana::exploded_graph const*, ana::sa ved_diagnostic*) (diagnostic-manager.cc:465) ==65008== by 0x1731EF3: ana::diagnostic_manager::emit_saved_diagnostics(ana:: exploded_graph const&) (diagnostic-manager.cc:616) ==65008== by 0xF87B77: ana::impl_run_checkers(ana::logger*) (engine.cc:4752) This bug exists since sometime before 20201206, with git hash 8c23434fdadcf4ca.
next reply other threads:[~2021-01-06 14:55 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-01-06 14:55 dcb314 at hotmail dot com [this message] 2021-01-06 15:41 ` [Bug analyzer/98564] " dmalcolm at gcc dot gnu.org 2021-01-07 2:43 ` cvs-commit at gcc dot gnu.org 2021-01-07 2:50 ` 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-98564-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).