Re:Show HN: Accelerating SHA256 by 100x in Golang on ARM
by pcwalton on Wednesday July 27, 2016 @10:53PM
(#12178046)
Opaque assembly blocks that the compiler doesn't understand the effects of are actually suboptimal for performance.
Re:Show HN: Accelerating SHA256 by 100x in Golang on ARM
by Cthulhu_ on Thursday July 28, 2016 @05:42AM
(#12179293)
Only if the compiler is aware of and can translate code into e.g. ARM-specific sha instructions. If not, then the developer is still smarter than the compiler and should use assembly to use those specific instructions.
Re:Show HN: Accelerating SHA256 by 100x in Golang on ARM
by dlsniper on Thursday July 28, 2016 @01:11AM
(#12178430)
Is this a general thing or a Go specific one? This generic statement seems to be false given how many optimizations that actually need assembly exist in Go and not only.
Re:Show HN: Accelerating SHA256 by 100x in Golang on ARM
by pjmlp on Thursday July 28, 2016 @08:20AM
(#12179722)
It is a general thing and quite common.
Either you keep adding intrisics to the compiler, or outsource it to an external Assembler.
Even managed languages have bytecode Assemblers available.
Re:Show HN: Accelerating SHA256 by 100x in Golang on ARM
by drchickensalad on Thursday July 28, 2016 @12:23AM
(#12178306)
Generally yes, specialized no.
I'm not sure why this should be a problem, it just shows attention to performance in my opinion.