On Jan 14, 4:23*am, Terje Mathisen "terje.mathisen at tmsw.no"
wrote:
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'.

I've thought about this in the context "execute alternating instructions
from both sides of the branch, adding implicit predicates to them", so
that when the branch retires the predicates become known and half the
instructions are cancelled.

This reminds me of a (not so useful) idea I posted here
21 Oct 2010, "Move on 'commit' predication?" Message-ID:

http://groups.google.com/group/comp....b5e80e5fd36288

It was basically just a (wrong-headed?) microarchitecture
for supporting dynamic predication (of hammock branches)
where one path was less likely but uncertain enough to
justify predication.

(One of the issues of eager execution is recognizing joining.)