On Mon, Apr 9, 2012 at 11:55 AM, Eric Botcazou <ebotca...@adacore.com> wrote:
> with the numerous checks generated in Ada, the gimplification process can
> generated dead branches that aren't easily eliminated at -O0 and can impair
> the debugging experience. We have found that unconditionally cleaning up the
> CFG before emitting the prologue/epilogue can help in some cases. This is the
> same idiom already used in rest_of_handle_jump2 for example.
> Tested on x86_64-suse-linux. Comments?
Isn't the gimple cfg-cleanup we run post optimization (right before expansion)
not enough? Or the cfg-cleanup we perform right after expansion now?
At least if the branches are really caused by the gimplification process I would
expect things to be cleaned up at this point, no?
> 2012-04-09 Eric Botcazou <ebotca...@adacore.com>
> * function.c (rest_of_handle_thread_prologue_and_epilogue): Clean up
> the CFG before generating prologue/epilogue even when not optimizing.
> Eric Botcazou