News for hackers. Stuff that matters.
Re:The State of Go: Where we are in February 2016 by vardump on Wednesday February 03, 2016 @01:26PM (#11028420)
> Ah yeah, I wasn't sure if fusion was going to happen.

Well, I didn't profile that case. Who knows what will really happen. Modern x86 processors are hard to understand.

> ... while the second cmp is against memory, data dependent on the register index

Hmm... that sounds like something that would dominate the cost? Memory access and data dependency. Ouch.

Also of course in that case, second compare+branch can't be fused, because cmp has a memory operand.

There are no comments on this comment yet.