Re:The Mill CPU Architecture – The Compiler [video]
by benou on Thursday July 09, 2015 @11:35AM
(#9858472)
I am curious about how does it compare to streaming loads? It is a common technic to avoid cache misses when you have a large number of registers, you can issue loads in advance, by-passing the cache, and the CPU will manage the data dependency in HW. The idea is that hopefully when the you will use the register, its data will already be available. Otherwise you stall as usual.
[ Parent
| on HN ]
Re:The Mill CPU Architecture – The Compiler [video]
by willvarfar on Thursday July 09, 2015 @12:40PM
(#9859002)
There are many facets to this. From a great height they are roughly simular, but in the details they differ.
For example, the Mill is a belt machine and each stack frame has its own belt and the hardware takes care of spilling in-flights across calls to any depth. Also, the Mill loads are orthogonal to cache management and we offer immunity to aliasing and false sharing.