public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "zsojka at seznam dot cz" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/64391] New: ICE: SIGSEGV in get_attrs_for (trans-mem.c:179) with -fgnu-tm and #pragma GCC ivdep Date: Tue, 23 Dec 2014 18:58:00 -0000 [thread overview] Message-ID: <bug-64391-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64391 Bug ID: 64391 Summary: ICE: SIGSEGV in get_attrs_for (trans-mem.c:179) with -fgnu-tm and #pragma GCC ivdep Product: gcc Version: 5.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: middle-end Assignee: unassigned at gcc dot gnu.org Reporter: zsojka at seznam dot cz Created attachment 34324 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=34324&action=edit reduced testcase Compiler output: $ gcc -fgnu-tm testcase.c -wrapper valgrind,-q ==19617== Invalid read of size 2 ==19617== at 0xC5B0A4: get_attrs_for(tree_node const*) (trans-mem.c:179) ==19617== by 0xC5DE28: is_tm_may_cancel_outer(tree_node*) (trans-mem.c:320) ==19617== by 0xC5E147: diagnose_tm_1(gimple_stmt_iterator*, bool*, walk_stmt_info*) (trans-mem.c:668) ==19617== by 0x9FC9CE: walk_gimple_stmt(gimple_stmt_iterator*, tree_node* (*)(gimple_stmt_iterator*, bool*, walk_stmt_info*), tree_node* (*)(tree_node**, int*, void*), walk_stmt_info*) (gimple-walk.c:551) ==19617== by 0x9FCC08: walk_gimple_seq_mod(gimple_statement_base**, tree_node* (*)(gimple_stmt_iterator*, bool*, walk_stmt_info*), tree_node* (*)(tree_node**, int*, void*), walk_stmt_info*) (gimple-walk.c:66) ==19617== by 0x9FCAB2: walk_gimple_stmt(gimple_stmt_iterator*, tree_node* (*)(gimple_stmt_iterator*, bool*, walk_stmt_info*), tree_node* (*)(tree_node**, int*, void*), walk_stmt_info*) (gimple-walk.c:579) ==19617== by 0x9FCC08: walk_gimple_seq_mod(gimple_statement_base**, tree_node* (*)(gimple_stmt_iterator*, bool*, walk_stmt_info*), tree_node* (*)(tree_node**, int*, void*), walk_stmt_info*) (gimple-walk.c:66) ==19617== by 0x9FCCA6: walk_gimple_seq(gimple_statement_base*, tree_node* (*)(gimple_stmt_iterator*, bool*, walk_stmt_info*), tree_node* (*)(tree_node**, int*, void*), walk_stmt_info*) (gimple-walk.c:96) ==19617== by 0xC5DEC2: diagnose_tm_blocks (trans-mem.c:862) ==19617== by 0xC5DEC2: (anonymous namespace)::pass_diagnose_tm_blocks::execute(function*) (trans-mem.c:891) ==19617== by 0xB5E85E: execute_one_pass(opt_pass*) (passes.c:2311) ==19617== by 0xB5ECD5: execute_pass_list_1(opt_pass*) [clone .constprop.73] (passes.c:2363) ==19617== by 0xB5ED28: execute_pass_list(function*, opt_pass*) (passes.c:2374) ==19617== Address 0x0 is not stack'd, malloc'd or (recently) free'd ==19617== testcase.c: In function 'foo': testcase.c:2:1: internal compiler error: Segmentation fault foo (void) ^ Please submit a full bug report, with preprocessed source if appropriate. See <http://gcc.gnu.org/bugs.html> for instructions. Tested revisions: r219043 - ICE 4_9 r219040 - ICE 4_8 - ignoring #pragma GCC ivdep
next reply other threads:[~2014-12-23 18:58 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-12-23 18:58 zsojka at seznam dot cz [this message] 2014-12-23 19:55 ` [Bug middle-end/64391] " zsojka at seznam dot cz 2015-01-13 13:09 ` mpolacek at gcc dot gnu.org 2015-01-13 13:55 ` mpolacek at gcc dot gnu.org 2015-01-13 20:23 ` mpolacek at gcc dot gnu.org 2015-01-13 20:25 ` mpolacek at gcc dot gnu.org 2015-01-14 8:44 ` mpolacek at gcc dot gnu.org 2015-01-14 8:48 ` mpolacek 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-64391-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).