On 02/02/2017 06:49 AM, Jan Hubicka wrote:
Hi,
it seems I forgot to send the updated patch. Here it is.
We now dump info like:
Checking profitability of path: 5 (16 insns) 3 (2 insns) 34 (2 insns) 33 (4
insns) 32 (1 insns) 10 (3 insns) 6
Control statement insns: 16
Overall: 12 insns
Registering FSM jump thread: (6, 10) incoming edge; (10, 32) (32, 33) (33,
34) (34, 3) (3, 5) (5, 16) nocopy; (5, 16)
path is printed backwards. It is how the loop process it.
Yea. I've always found that confusing, particularly since the other
threaders go the other direction.
One thing on the todo list is to stop converting between the two
recording formats and remove the forward/backwards threading
entanglement in tree-ssa-threadupdate.c.
Anyway, the patch looks fine to me as well (please fix the nits Richi
pointed out).
jeff
