[Bug tree-optimization/68892] [6 Regression] Excessive dead loads produced by BB vectorization
rguenth at gcc dot gnu.org
gcc-bugzilla@gcc.gnu.org
Thu Dec 17 08:37:00 GMT 2015
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68892
--- Comment #6 from Richard Biener <rguenth at gcc dot gnu.org> ---
(In reply to Bill Seurer from comment #5)
> It also causes an ice when I compile 20100610.c
>
> seurer@genoa:~/tests/gcc$ ~/gcc/install/gcc-test3/bin/gcc -c -fgnu-tm -O3
> 20100610.c
> In function 'TMelement_alloc':
> cc1: internal compiler error: tree check: expected tree that contains 'decl
> common' structure, have 'ssa_name' in prepare_gimple_addressable, at
> gimplify.c:3308
> 0x10b42f0b tree_contains_struct_check_failed(tree_node const*,
> tree_node_structure_enum, char const*, int, char const*)
> /home/seurer/gcc/gcc-test3/gcc/tree.c:9778
> 0x10567f3f contains_struct_check(tree_node*, tree_node_structure_enum, char
> const*, int, char const*)
> /home/seurer/gcc/gcc-test3/gcc/tree.h:3111
> 0x10567f3f prepare_gimple_addressable
> /home/seurer/gcc/gcc-test3/gcc/gimplify.c:3308
> 0x1055ba37 gimplify_addr_expr
> /home/seurer/gcc/gcc-test3/gcc/gimplify.c:5081
> 0x1055ba37 gimplify_expr(tree_node**, gimple**, gimple**, bool
> (*)(tree_node*), int)
> /home/seurer/gcc/gcc-test3/gcc/gimplify.c:10162
> 0x1057b81b force_gimple_operand_1(tree_node*, gimple**, bool
> (*)(tree_node*), tree_node*)
> /home/seurer/gcc/gcc-test3/gcc/gimplify-me.c:78
> 0x1057ba1f force_gimple_operand_gsi_1(gimple_stmt_iterator*, tree_node*,
> bool (*)(tree_node*), tree_node*, bool, gsi_iterator_update)
> /home/seurer/gcc/gcc-test3/gcc/gimplify-me.c:115
> 0x10838cf3 gimplify_addr
> /home/seurer/gcc/gcc-test3/gcc/trans-mem.c:1183
> 0x10844153 expand_assign_tm
> /home/seurer/gcc/gcc-test3/gcc/trans-mem.c:2330
> 0x1084560b expand_block_tm
> /home/seurer/gcc/gcc-test3/gcc/trans-mem.c:2516
> 0x1084560b execute_tm_mark
> /home/seurer/gcc/gcc-test3/gcc/trans-mem.c:3014
> 0x1084560b execute
> /home/seurer/gcc/gcc-test3/gcc/trans-mem.c:3059
Can you please open new bugs for these issues? This one at least looks
unrelated.
More information about the Gcc-bugs
mailing list