public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "hjl dot tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/39010] New: [LTO] Memory corruption on gcc.c-torture/compile/limits-fndefn.c Date: Wed, 28 Jan 2009 20:38:00 -0000 [thread overview] Message-ID: <bug-39010-682@http.gcc.gnu.org/bugzilla/> (raw) On Linux/x86-64, revision 143741 # valgrind --tool=memcheck /export/gnu/import/svn/gcc-test/bld/gcc/cc1 -quiet -v -imultilib 32 -iprefix /export/gnu/import/svn/gcc-test/bld/gcc/../lib/gcc/x86_64-unknown-linux-gnu/4.4.0/ -isystem /export/gnu/import/svn/gcc-test/bld/gcc/include -isystem /export/gnu/import/svn/gcc-test/bld/gcc/include-fixed /export/gnu/import/svn/gcc-test/src-lto/gcc/testsuite/gcc.c-torture/compile/limits-fndefn.c -quiet -dumpbase limits-fndefn.c -m32 -mtune=generic -auxbase limits-fndefn -w -version -flto -o limits-fndefn.s zsh: correct 'limits-fndefn.c' to 'limits-fndefn.s' [nyae]? ==5452== Memcheck, a memory error detector. ==5452== Copyright (C) 2002-2007, and GNU GPL'd, by Julian Seward et al. ==5452== Using LibVEX rev 1804, a library for dynamic binary translation. ==5452== Copyright (C) 2004-2007, and GNU GPL'd, by OpenWorks LLP. ==5452== Using valgrind-3.3.0, a dynamic binary instrumentation framework. ==5452== Copyright (C) 2000-2007, and GNU GPL'd, by Julian Seward et al. ==5452== For more details, rerun with: -v ==5452== ignoring nonexistent directory "/export/gnu/import/svn/gcc-test/bld/gcc/../lib/gcc/x86_64-unknown-linux-gnu/4.4.0/include" ignoring nonexistent directory "/export/gnu/import/svn/gcc-test/bld/gcc/../lib/gcc/x86_64-unknown-linux-gnu/4.4.0/include-fixed" ignoring nonexistent directory "/export/gnu/import/svn/gcc-test/bld/gcc/../lib/gcc/x86_64-unknown-linux-gnu/4.4.0/../../../../x86_64-unknown-linux-gnu/include" ignoring nonexistent directory "/usr/local/lib/gcc/x86_64-unknown-linux-gnu/4.4.0/include" ignoring nonexistent directory "/usr/local/lib/gcc/x86_64-unknown-linux-gnu/4.4.0/include-fixed" ignoring nonexistent directory "/usr/local/lib/../x86_64-unknown-linux-gnu/include" #include "..." search starts here: #include <...> search starts here: /export/gnu/import/svn/gcc-test/bld/gcc/include /export/gnu/import/svn/gcc-test/bld/gcc/include-fixed /usr/local/include /usr/include End of search list. GNU C (lto merged with rev 143693) version 4.4.0 20090127 (experimental) [lto revision 143741] (x86_64-unknown-linux-gnu) compiled by GNU C version 4.4.0 20090127 (experimental) [lto revision 143741], GMP version 4.2.2, MPFR version 2.3.2. GGC heuristics: --param ggc-min-expand=30 --param ggc-min-heapsize=4096 Compiler executable checksum: 422ba1b8d5a8cc825fd0dfb4279ac4e7 ==5452== Invalid read of size 1 ==5452== at 0xB908AF: htab_hash_string (hashtab.c:812) ==5452== by 0xB90F0B: htab_expand (hashtab.c:540) ==5452== by 0xB91269: htab_find_slot_with_hash (hashtab.c:619) ==5452== by 0xB23D54: output_string (lto-function-out.c:275) ==5452== by 0xB242AE: output_tree_flags (lto-function-out.c:532) ==5452== by 0xB27E9D: output_local_vars (lto-function-out.c:1283) ==5452== by 0xB2D0A9: lto_output (lto-function-out.c:1968) ==5452== by 0x667AC8: ipa_write_summaries_2 (passes.c:1403) ==5452== by 0x66899C: ipa_write_summaries_1 (passes.c:1428) ==5452== by 0x668A63: ipa_write_summaries (passes.c:1449) ==5452== by 0x8E3A62: cgraph_optimize (cgraphunit.c:1266) ==5452== by 0x416732: c_write_global_declarations (c-decl.c:8045) ==5452== Address 0x4d2625e is 0 bytes after a block of size 6 alloc'd ==5452== at 0x4A0739E: malloc (vg_replace_malloc.c:207) ==5452== by 0xB928A7: xmalloc (xmalloc.c:147) ==5452== by 0xB23DD9: output_string (lto-function-out.c:283) ==5452== by 0xB27DCC: output_local_vars (lto-function-out.c:1241) ==5452== by 0xB2D0A9: lto_output (lto-function-out.c:1968) ==5452== by 0x667AC8: ipa_write_summaries_2 (passes.c:1403) ==5452== by 0x66899C: ipa_write_summaries_1 (passes.c:1428) ==5452== by 0x668A63: ipa_write_summaries (passes.c:1449) ==5452== by 0x8E3A62: cgraph_optimize (cgraphunit.c:1266) ==5452== by 0x416732: c_write_global_declarations (c-decl.c:8045) ==5452== by 0x70FD6C: toplev_main (toplev.c:991) ==5452== by 0x3A0D01E575: (below main) (in /lib64/libc-2.9.so) -- Summary: [LTO] Memory corruption on gcc.c-torture/compile/limits- fndefn.c Product: gcc Version: lto Status: UNCONFIRMED Severity: normal Priority: P3 Component: middle-end AssignedTo: dnovillo at google dot com ReportedBy: hjl dot tools at gmail dot com http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39010
next reply other threads:[~2009-01-28 20:38 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-01-28 20:38 hjl dot tools at gmail dot com [this message] 2009-01-30 21:09 ` [Bug lto/39010] " hjl dot tools at gmail dot com 2009-01-30 21:22 ` hjl dot tools at gmail dot com 2009-01-30 21:55 ` hjl at gcc dot gnu dot org 2009-01-30 21:58 ` hjl dot tools at gmail dot com 2009-01-31 18:49 ` dnovillo at gcc dot gnu dot org 2009-01-31 18:51 ` dnovillo at gcc dot gnu dot org 2009-02-17 14:26 ` espindola at gcc dot gnu dot org 2009-07-08 6:07 ` bje at gcc dot gnu dot 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-39010-682@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).