On 08/21/14 04:30, Richard Biener wrote:
It turns Jeff's jump-threading code in to a strange franken-pass of bits and
pieces of detection and optimisation, and would need some substantial
reworking to fit in with Jeff's changes last Autumn, but if it is more
likely to be acceptable for trunk then perhaps we could look to revive it.
It would be nice to reuse the path copy code Jeff added last year, but I
don't have much intuition as to how feasible that is.
Was this the sort of thing that you were imagining?
Yeah, didn't look too closely though.
It'd be pretty ugly I suspect. But it's probably worth pondering since
that approach would eliminate the concerns about the cost of detection
(which is problematical for the jump threader) by using Steve's code for
that.
On the update side, I suspect most, if not all of the framework is in
place to handle this kind of update if the right threading paths were
passed to the updater. I can probably cobble together that by-hand and
see what the tree-ssa-threadupdate does with it. But it'll be a week or
so before I could look at it.
jeff
