https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86422
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |WAITING
--- Comment #7 from Richard Biener <rguenth at gcc dot gnu.org> ---
Yeah, so there's into-SSA for example:
#63 0x0000000001368cd6 in prepare_block_for_update (
bb=<basic_block 0x7fffdd071e38 (220676)>, insert_phi_p=true)
at /space/rguenther/src/svn/gcc-8-branch/gcc/tree-into-ssa.c:2677
2677 prepare_block_for_update (son, insert_phi_p);
(gdb) l
2672
2673 /* Now visit all the blocks dominated by BB. */
2674 for (son = first_dom_son (CDI_DOMINATORS, bb);
2675 son;
2676 son = next_dom_son (CDI_DOMINATORS, son))
2677 prepare_block_for_update (son, insert_phi_p);
and there are many more in the tree.
So, can you check your stack ulimit and see if raising it solves the issue for
you (memory usage is still very high though).
