4 ms·
> seems to use thread level speculation If the software is compiled into a normal single threaded program then what else there is left except instruction level
by sharpneli 12y ago
> seems to use thread level speculation
If the software is compiled into a normal single threaded program then what else there is left except instruction level parallelism?
And if you can compile it to work with two threads then we have Hyperthreading to take advantage of that even with a single core.
Their [Soft Machines] latest patent is about basically an OoO method in overdrive, it abuses only instruction level parallelism. And based on that their claim that their pipeline would be short is not really valid.
- cfallin 12y agoThread-level speculation is exploiting ILP. In some contexts it's compiler-assisted but in this context I would imagine it is fully microarchitectural (i.e., in hardware/translation firmware, running a single instruction stream of user code, invisible to the user). Dynamic multithreading (Akkary 1998?) did this by splitting the thread at predictable points like function calls/returns and (IIRC) backward branches. So it's still ILP within a single thread, but at a much longer distance than what an OoO scheduling window provides.