public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ktkachov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/59270] [4.9 Regression] [c++11] ICE with decltype of a broken class Date: Wed, 15 Jan 2014 10:58:00 -0000 [thread overview] Message-ID: <bug-59270-4-qV5MMLbHqT@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-59270-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59270 ktkachov at gcc dot gnu.org changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ktkachov at gcc dot gnu.org --- Comment #2 from ktkachov at gcc dot gnu.org --- I'm seeing a similar ICE when testing cilk plus on arm: $TOP/gcc/gcc/testsuite/c-c++-common/cilk-plus/AN/rank_mismatch2.c:19:25: internal compiler error: tree check: expected class 'type', have 'exceptional' (error_mark) in create_tmp_from_val, at gimplify.c:456 0xbea6bd tree_class_check_failed(tree_node const*, tree_code_class, char const*, int, char const*) $TOP/gcc/gcc/tree.c:9243 0x822ca6 tree_class_check $TOP/gcc/gcc/tree.h:2832 0x822ca6 create_tmp_from_val $TOP/gcc/gcc/gimplify.c:456 0x822ca6 lookup_tmp_var $TOP/gcc/gcc/gimplify.c:493 0x822ca6 internal_get_tmp_var $TOP/gcc/gcc/gimplify.c:523 0x82369e gimplify_save_expr $TOP/gcc/gcc/gimplify.c:4710 0x810bb7 gimplify_expr(tree_node**, gimple_statement_base**, gimple_statement_base**, bool (*)(tree_node*), int) $TOP/gcc/gcc/gimplify.c:7720 0x816fd8 gimplify_stmt(tree_node**, gimple_statement_base**) $TOP/gcc/gcc/gimplify.c:5334 0x817de3 gimplify_compound_expr $TOP/gcc/gcc/gimplify.c:4665 0x8101fb gimplify_expr(tree_node**, gimple_statement_base**, gimple_statement_base**, bool (*)(tree_node*), int) $TOP/gcc/gcc/gimplify.c:7430 0x816fd8 gimplify_stmt(tree_node**, gimple_statement_base**) $TOP/gcc/gcc/gimplify.c:5334 0x810243 gimplify_statement_list $TOP/gcc/gcc/gimplify.c:1405 0x810243 gimplify_expr(tree_node**, gimple_statement_base**, gimple_statement_base**, bool (*)(tree_node*), int) $TOP/gcc/gcc/gimplify.c:7849 0x816fd8 gimplify_stmt(tree_node**, gimple_statement_base**) $TOP/gcc/gcc/gimplify.c:5334 0x8181d3 gimplify_bind_expr $TOP/gcc/gcc/gimplify.c:1072 0x8106cd gimplify_expr(tree_node**, gimple_statement_base**, gimple_statement_base**, bool (*)(tree_node*), int) $TOP/gcc/gcc/gimplify.c:7631 0x816fd8 gimplify_stmt(tree_node**, gimple_statement_base**) $TOP/gcc/gcc/gimplify.c:5334 0x81712a gimplify_body(tree_node*, bool) $TOP/gcc/gcc/gimplify.c:8541 0x817771 gimplify_function_tree(tree_node*) $TOP/gcc/gcc/gimplify.c:8694 0x6a8797 analyze_function $TOP/gcc/gcc/cgraphunit.c:649 Please submit a full bug report, with preprocessed source if appropriate. Please include the complete backtrace with any bug report. See <http://gcc.gnu.org/bugs.html> for instructions.
next prev parent reply other threads:[~2014-01-15 10:58 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-11-23 23:26 [Bug c++/59270] New: " reichelt at gcc dot gnu.org 2013-11-25 9:16 ` [Bug c++/59270] " rguenth at gcc dot gnu.org 2014-01-15 10:52 ` paolo.carlini at oracle dot com 2014-01-15 10:58 ` ktkachov at gcc dot gnu.org [this message] 2014-01-15 11:00 ` paolo.carlini at oracle dot com 2014-01-15 11:30 ` ktkachov at gcc dot gnu.org 2014-01-17 20:25 ` paolo at gcc dot gnu.org 2014-01-17 20:26 ` paolo.carlini at oracle 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-59270-4-qV5MMLbHqT@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).