On 1/13/2012 8:16 PM, Joe keane wrote:
In ,
Andy (Super) wrote:
Problem is that eager threads seldom last long, so it is hard for eager
threads to overcome the cost of migrating to another core.

Essentially creating a new thread, for every -branch-, falls into the
'that don't sound right'.

Nobody would seriously propose a new thread for every branch.

You would only consider eager threading for flakey branches, where you
don't know which way they are going to go. And won't know for a while.

Myself, I think non-threading approaches to eager execution are better.
E.g. the discussion of short forward branches - emit colde that
computes both sides of such a hammock, with operations like Phi nodes to
bring back rto a single dataflow.