News for hackers. Stuff that matters.
Re:WTL (Wave Threshold Logic) Primer by thesz on Monday April 11, 2016 @08:22AM (#11471006)
This is good old asynchronous logic with separate no-data state, renamed (probably, for patent reasons).
Re:WTL (Wave Threshold Logic) Primer by throwaway000002 on Monday April 11, 2016 @11:46AM (#11472303)
I did post about them earlier. [1]

I think there may be some novelty to the design of their "threshold gate" at the silicon level to avoid metastability issues and thus enable their design tool flow.

They seem to have since pivoted, though, to something akin to neuromorphic computing popularized by the large asynchronous circuitry in IBM's TrueNorth chip.

The work towards making deep learning power-efficient will be important, and I think that's where they're heading.

There are area tradeoffs, but if you have efficiency gain, then you can take advantage of "dark-silicon".

Asynchronous design's time may really indeed be coming. [2]

[1] https://news.ycombinator.com/item?id=10625233

[2] https://news.ycombinator.com/item?id=11425533

Re:WTL (Wave Threshold Logic) Primer by thesz on Monday April 11, 2016 @02:18PM (#11473867)
Having no-data symbol in the alphabet is a sure-fire way to have very stable circuitry. I am rusty in the details (I did development a long time ago and not returned for a while), but for O(width) AND-NOTs, two Miller C elements and glitch-free synthesis you can get async logic without metastability issues, just by design.

There is a Russian chip named NeuroMatrix: https://en.wikipedia.org/wiki/NeuroMatrix

It's main accelerator exploits the idea that deep neural networks need less precision in layers closer to output. So it uses variable-width variable-count multiply-add circuit within single 64x64 multiply-add circuit. At the start there are, say, only two multiplications done, 32x64, but in the last layer you can fire up to 64 multiplications.

Was this circuit built with async logic, it will be even faster, because in clocked logic they have to control depth to get to clock frequency for worst case (1x64x64) and can't gain anything except multiplication count for 64x1x1 case. In async setting, the use in the 64x1x1 would be blazingly fast - one bit depth!

(I can be wrong here and there - right now I am editing VHDL grammar, adapting it for ANTLR4, sorry; I hope you get the idea, though)

I don't know how DeepNorth operates. But I believe they use the same trick or something close to it - it's cheap and impressive.

Re:WTL (Wave Threshold Logic) Primer by DigitalJack on Monday April 11, 2016 @01:18PM (#11473268)