News for hackers. Stuff that matters.

A comment on Google removes SIMD.js support from Chromium. Parent comment

Re:Google removes SIMD.js support from Chromium by sillysaurus3 on Sunday June 04, 2017 @12:08AM (#14479839)
Yep, bingo. There's no substitute for understanding exactly what's being emitted in the innermost loops of intensive operations.

I wonder whether any of this matters much in GPU-land though. I haven't kept up with the game, so the young hotshots that programmed AlphaGo might be doing all of that without resorting to low-level-ASM-type sorcery. I wouldn't be surprised if massive parallelism makes these types of gains a rounding error.

[ Parent | on HN ]
Re:Google removes SIMD.js support from Chromium by Houshalter on Sunday June 04, 2017 @12:41AM (#14479918)
AlphaGo as far as I know just uses standard matrix math libraries to do stuff on the GPU.
[ Parent | on HN ]
Re:Google removes SIMD.js support from Chromium by johnsmith21006 on Sunday June 04, 2017 @05:19PM (#14483564)
AlphaGo does not use GPUs but instead the TPUs.

"AlphaGo was powered by TPUs in the matches against Go world champion, Lee Sedol, enabling it to "think" much faster and look farther ahead between moves."

[ Parent | on HN ]
Re:Google removes SIMD.js support from Chromium by Houshalter on Sunday June 04, 2017 @07:45PM (#14484363)
It used to use GPUs for training because I don't think the first gen TPUs could do training.
[ Parent | on HN ]