This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug tree-optimization/46879] [4.6 Regression] ICE: in separate_decls_in_region_debug_bind, at tree-parloops.c:778 with -flto -ftree-parallelize-loops -gdwarf-3
- From: "rguenth at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Fri, 10 Dec 2010 15:21:35 +0000
- Subject: [Bug tree-optimization/46879] [4.6 Regression] ICE: in separate_decls_in_region_debug_bind, at tree-parloops.c:778 with -flto -ftree-parallelize-loops -gdwarf-3
- Auto-submitted: auto-generated
- References: <bug-46879-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46879
--- Comment #2 from Richard Guenther <rguenth at gcc dot gnu.org> 2010-12-10 15:21:28 UTC ---
(In reply to comment #1)
> This looks like a lto bug to me.
> 1765 tree *basep = &op;
> 1766 while (handled_component_p (*basep))
> 1767 basep = &TREE_OPERAND (*basep, 0);
> 1768 if (TREE_CODE (*basep) == VAR_DECL
> 1769 && !auto_var_in_fn_p (*basep, current_function_decl))
> 1770 {
> 1771 bool volatilep = TREE_THIS_VOLATILE (*basep);
> 1772 *basep = build2 (MEM_REF, TREE_TYPE (*basep),
> 1773 build_fold_addr_expr (*basep),
> 1774 build_int_cst (build_pointer_type
> 1775 (TREE_TYPE (*basep)), 0));
> 1776 TREE_THIS_VOLATILE (*basep) = volatilep;
> 1777 }
>
> in output_gimple_stmt is not suitable for the first argument of a GIMPLE_DEBUG
> stmt - where the argument must be a DECL.
Hm, well. Then the debug machinery has to deal with type mismatches I guess.
But I wonder why we have debug-stmts for global variables anyway? I thought
they are only used for registers.