On Mon, Apr 9, 2012 at 6:11 PM, Eric Botcazou ebotca...@adacore.com wrote:
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
Hi,
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
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?
At least the
