This field has a well established name: asynchronous logic/circuit.<p>The author of the article failed to even mention once this term, instead repeating the term “clockless” as he was in some kind of branding spree.<p>Furthermore one of the article's tags was “apple”, despite AFAIK the content not being affiliated with apple in any way.
Another very interesting async design is GreenArrays GA144:
"This very powerful and versatile chip consists of an 18x8 array of architecturally identical, independent, complete F18A computers, or nodes, each of which operates asynchronously. Each computer is capable of performing a basic ALU instruction in ~1.5 nanoseconds for an energy cost on the order of 7 picojoules".
Programmed in Forth.
<a href="http://www.greenarraychips.com/index.html" rel="nofollow">http://www.greenarraychips.com/index.html</a>
Not that the article is particularly detailed, but squinting at the clock diagram for Wave Semi, it appears to be a some kind of token passing, where the token is the clock.<p>I guess this question is for the semi- folks out there: given any n-bit boolean function, for smallish n, is there a way to implement the function so that the output is rock-stable (within reason) and only flips if given an input flip the corresponding function flips?<p>Because, if not, I don't see how this clock passing system won't require factoring in logic delay.<p>I'm sure a lot of details have been elided. Also, if it isn't apparent, I have no logic design knowledge.<p>All I know, from an outsider's perspective, having a global clock is ludicrous. When will designers finally kill it?! Us software people have had to kill the concept of intrinsic clocks with our consensus protocols for a while now...
I think there is a technological path for gradually introducing synchronous design in clocked world: you can give them clocked inputs without problem, and you can gate their output at their worst propagation time without problem either.<p>I think with such an easy technological path, there is no intrinsic reason not to have them around us, even exposed as clocked systems. If someone told me today that there already are synchronous blocks in a famous silicon chip I would certainly not be surprised.<p>For example, I'm not a silicon guy so I'm guessing, but adders are generally exposed as one cycle instructions in software, but they still have to propagate the carry on the width of the word, so I guess adders are simply a tree of gate that synchronously propagate and we know the carry propagates faster than the clock tick.
I recently asked an Intel chip designer if asynchronous circuits could be a way to deal with stalling of Moore's Law and he was adamant that asynchronous circuits are a "fantasy." His argument was that even though synchronous use about 20% of the energy on a modern, chips, with asynchronous you still need to pass around synchronization tokens which would double the energy required and worse it would be on the critical path.
Fulcrum Microsystems was a Clockless ASIC startup that was acquired by Intel in 2011 for their Ethernet switch silicon technology. <a href="http://newsroom.intel.com/community/intel_newsroom/blog/2011/07/19/intel-to-acquire-fulcrum-microsystems" rel="nofollow">http://newsroom.intel.com/community/intel_newsroom/blog/2011...</a>
See also, FLEET[1]. I'm surprised this hasn't gained more traction(or at least hype). I saw Sutherland give a talk about it in 2011/2012 or so.<p>[1]<a href="https://inst.eecs.berkeley.edu/~cs152/fa06/lecnotes/async.pdf" rel="nofollow">https://inst.eecs.berkeley.edu/~cs152/fa06/lecnotes/async.pd...</a>
I recently dropped a lot of links to asynchronous cell libraries, chips, and so on in this comment:<p><a href="https://news.ycombinator.com/item?id=10621937" rel="nofollow">https://news.ycombinator.com/item?id=10621937</a><p>Just in case pro's want to comment on any of it or think it's cool.
>They also had to invent a new type of gate – one that switches based on the sum of the number of its input that are at logic 1.<p>What? Isn't that just AND? I wasn't really too clever from looking at the diagram provided, so I might be missing something.
Leakage is the big problem in deep submicron. You can't keep a state without periodically refreshing it (cf. DRAM). Also, asynchronous circuits are very prone to metastability. If these problems were easily solved, we'd have seen this old idea be widespread by now.