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 rtl-optimization/64003] valgrind complains about get_attr_length_nobnd in insn-attrtab.c from i386.md Date: Thu, 20 Nov 2014 19:41:00 -0000 [thread overview] Message-ID: <bug-64003-4-HjRPQtm3M8@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-64003-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64003 --- Comment #5 from dmalcolm at gcc dot gnu.org --- Running valgrind with --track-origins=yes shows: ==9952== Uninitialised value was created by a heap allocation ==9952== at 0x4A0645D: malloc (in /usr/lib64/valgrind/vgpreload_memcheck-amd64-linux.so) ==9952== by 0x12BF3B7: xmalloc (xmalloc.c:147) ==9952== by 0x7876A4: shorten_branches(rtx_insn*) (final.c:1022) ==9952== by 0x787F5F: (anonymous namespace)::pass_shorten_branches::execute(function*) (final.c:4567) ==9952== by 0x994581: execute_one_pass(opt_pass*) (passes.c:2269) ==9952== by 0x994B95: execute_pass_list_1(opt_pass*) (passes.c:2321) ==9952== by 0x994BA7: execute_pass_list_1(opt_pass*) (passes.c:2322) ==9952== by 0x994BA7: execute_pass_list_1(opt_pass*) (passes.c:2322) ==9952== by 0x994BE8: execute_pass_list(function*, opt_pass*) (passes.c:2332) ==9952== by 0x6B87E3: cgraph_node::expand() (cgraphunit.c:1773) ==9952== by 0x6B9DB8: symbol_table::compile() (cgraphunit.c:1909) ==9952== by 0x6BB69C: symbol_table::finalize_compilation_unit() (cgraphunit.c:2325) specifically, it's reading uninitialized data from the insn_lengths array allocated here: insn_lengths = XNEWVEC (int, max_uid);
next prev parent reply other threads:[~2014-11-20 19:41 UTC|newest] Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-11-20 18:39 [Bug rtl-optimization/64003] New: " dmalcolm at gcc dot gnu.org 2014-11-20 18:41 ` [Bug rtl-optimization/64003] " dmalcolm at gcc dot gnu.org 2014-11-20 18:54 ` dmalcolm at gcc dot gnu.org 2014-11-20 19:23 ` dmalcolm at gcc dot gnu.org 2014-11-20 19:27 ` dmalcolm at gcc dot gnu.org 2014-11-20 19:41 ` dmalcolm at gcc dot gnu.org [this message] 2014-11-21 19:04 ` [Bug target/64003] " dmalcolm at gcc dot gnu.org 2014-12-02 2:20 ` dmalcolm at gcc dot gnu.org 2014-12-02 15:40 ` dmalcolm at gcc dot gnu.org 2014-12-02 15:48 ` dmalcolm at gcc dot gnu.org 2014-12-02 15:54 ` dmalcolm at gcc dot gnu.org 2014-12-02 16:08 ` dmalcolm at gcc dot gnu.org 2014-12-02 16:13 ` dmalcolm at gcc dot gnu.org 2014-12-04 9:24 ` amylaar at gcc dot gnu.org 2014-12-04 18:43 ` law at redhat dot com 2014-12-04 18:44 ` law at redhat dot com 2014-12-04 19:19 ` amylaar at gcc dot gnu.org 2014-12-04 19:38 ` enkovich.gnu at gmail dot com 2014-12-04 19:45 ` amylaar at gcc dot gnu.org 2014-12-04 19:51 ` law at redhat dot com 2014-12-04 19:54 ` law at redhat dot com 2014-12-05 10:07 ` enkovich.gnu at gmail dot com 2014-12-05 10:08 ` enkovich.gnu at gmail dot com 2014-12-05 10:38 ` ubizjak at gmail dot com 2014-12-05 10:50 ` ubizjak at gmail dot com 2014-12-05 14:19 ` rsandifo at gcc dot gnu.org 2014-12-05 15:01 ` enkovich.gnu at gmail dot com 2014-12-05 16:01 ` ienkovich at gcc dot gnu.org 2015-04-16 14:08 ` ienkovich at gcc dot gnu.org 2015-07-24 8:32 ` ubizjak at gmail dot com 2015-07-24 8:36 ` ubizjak at gmail dot com 2015-07-24 16:26 ` uros at gcc dot gnu.org 2015-07-24 16:31 ` ubizjak at gmail dot com
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-64003-4-HjRPQtm3M8@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).