public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dimhen at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/59350] [4.9 regression] ICE: in vt_expand_var_loc_chain, at var-tracking.c:8212 Date: Tue, 10 Dec 2013 17:04:00 -0000 [thread overview] Message-ID: <bug-59350-4-wP9EtMBK8F@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-59350-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59350 --- Comment #10 from Dmitry G. Dyachenko <dimhen at gmail dot com> --- (In reply to Dmitry G. Dyachenko from comment #8) valgrind' messages looks unrelated to ICE. I rebuild r205461 with memset(set, {0,0x42}, n_bytes) instead of VALGRIND_DISCARD (VALGRIND_MAKE_MEM_DEFINED (set, n_bytes)) in sparseset.c::sparseset_alloc() without luck. But I see one strangeness: according to /proc/cpuinfo I have Intel(R) Core i5/760. Gcc is build with arch/tune=native, but while running selects tune/arch=i7.
next prev parent reply other threads:[~2013-12-10 17:04 UTC|newest] Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-11-29 22:06 [Bug middle-end/59350] New: " dimhen at gmail dot com 2013-12-02 12:45 ` [Bug middle-end/59350] " rguenth at gcc dot gnu.org 2013-12-04 14:55 ` rmansfield at qnx dot com 2013-12-05 8:16 ` dimhen at gmail dot com 2013-12-10 7:43 ` jakub at gcc dot gnu.org 2013-12-10 10:04 ` dimhen at gmail dot com 2013-12-10 11:54 ` jakub at gcc dot gnu.org 2013-12-10 13:23 ` dimhen at gmail dot com 2013-12-10 13:23 ` dimhen at gmail dot com 2013-12-10 14:27 ` rmansfield at qnx dot com 2013-12-10 17:04 ` dimhen at gmail dot com [this message] 2013-12-10 17:27 ` dimhen at gmail dot com 2013-12-13 9:03 ` ebotcazou at gcc dot gnu.org 2013-12-13 9:03 ` ebotcazou at gcc dot gnu.org 2013-12-14 11:26 ` [Bug rtl-optimization/59350] " ebotcazou at gcc dot gnu.org 2013-12-14 15:26 ` ebotcazou at gcc dot gnu.org 2013-12-14 15:27 ` ebotcazou at gcc dot gnu.org 2013-12-15 9:17 ` dimhen at gmail dot com 2013-12-15 10:36 ` ebotcazou at gcc dot gnu.org 2013-12-15 10:40 ` dimhen at gmail dot com 2013-12-15 10:47 ` dimhen at gmail dot com 2013-12-15 11:07 ` ebotcazou at gcc dot gnu.org 2013-12-15 11:10 ` dimhen at gmail dot com 2013-12-15 11:16 ` dimhen at gmail dot com 2013-12-15 12:32 ` ebotcazou at gcc dot gnu.org 2013-12-15 15:49 ` dimhen at gmail dot com 2013-12-15 19:08 ` dimhen at gmail dot com 2013-12-16 9:45 ` ktkachov at gcc dot gnu.org 2013-12-16 10:57 ` ebotcazou at gcc dot gnu.org 2013-12-16 11:42 ` ktkachov at gcc dot gnu.org 2013-12-17 13:02 ` dcb314 at hotmail dot com 2013-12-17 13:03 ` dcb314 at hotmail dot com 2013-12-17 16:03 ` ebotcazou at gcc dot gnu.org 2013-12-19 15:37 ` rguenth at gcc dot gnu.org 2013-12-19 16:12 ` dcb314 at hotmail dot com 2014-01-06 11:39 ` [Bug debug/59350] " ebotcazou at gcc dot gnu.org 2014-01-06 11:40 ` ebotcazou at gcc dot gnu.org 2014-01-06 19:45 ` dimhen 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-59350-4-wP9EtMBK8F@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).