3 ms·
> ...while being able to move all of the speculation into the dynamic recompilation layer. Or move it all into static analysis. You might be interested in the
by ansible 6y ago
> ...while being able to move all of the speculation into the dynamic recompilation layer.
Or move it all into static analysis. You might be interested in the Mill CPU architecture:
https://millcomputing.com/docs/ https://millcomputing.com/docs/
Very Very Very Long Instruction Word system, without a conventional register file. All of the speculation that is done in hardware on a conventional CPU is pushed back to the compiler.
More about Spectre, Meltdown and the Mill here:
https://millcomputing.com/blog/wp-content/uploads/2018/01/Spectre.03.pdf https://millcomputing.com/blog/wp-content/uploads/2018/01/Sp...
- KMag 6y agoYea, that sort of dataflow analysis (at static compile or just-in-time compile time) is what I'm getting at for avoiding Spectre/Meltdown, but with the added ability of being able to use profiling information to re-generate the code paths where you're getting pipeline stalls due to flaws in the assumptions used in static instruction scheduling.