Re:Why are my Go executable files so large?
by temac on Sunday December 29, 2019 @03:14PM
(#21908140)
Even with store-load fw, you get a penalty (~3 cycle latency) over register accesses, no?
[ Parent
| on HN ]
Re:Why are my Go executable files so large?
by Jasper_ on Sunday December 29, 2019 @03:44PM
(#21908330)
yeah, but it's cheaper than full L1 hit, which is where it would go if not for that.
Re:Why are my Go executable files so large?
by temac on Sunday December 29, 2019 @04:11PM
(#21908507)
I was trying to cite a typical full L1 hit latency... I thought store-load fw simply avoid having to flush the complete write buffer before the access is even possible, which risk to take far more than ~3 cycles. Now maybe it can be faster in some cases than an L1 hit, I don't know.
Edit: it seems that store-load forwarding is actually slightly slower than L1: https://www.agner.org/optimize/blog/read.php?i=854#854