"If Intel gets big into fully synthesizable circuits then they will do for synthesis tools what they did for computational lithography, and everyone will benefit from Intel's push for solid and reliable software design tools"
could u pls explain this in english. thanks
What does that mean, in layman's terms? I assume it has nothing to do with Korg.
I don't know where to begin because I'm not really sure how familiar or unfamiliar you folks are with computer-aided layout and automated design tools?
I could try an analogy but odds are high I'll just be rebuked by a handful of "your analogies suck ass" responses...
Let see, how about if I use building a bridge as an example. As a civil engineer you might build a bridge based on specific local geography attributes (how long of a span does the bridge need to cover?), factor in the amount of peak road traffic the bridge needs to endure, and perhaps a preference for building materials based on knowledge of the local weather (concrete and climates that regularly freeze in the winter usually don't work out well, vice versa for steel structures in warm humid tropical climates, etc).
So you, as the engineer, could design said bridge the old-skool way of laying out trusses and support members in CAD or with some other "hand layout" software program, computing stresses and strains and cost, etc. Then tweaking the design by hand to reduce material usage or to improve weight-to-load carrying efficiency and so on until you were ok with the finalized design.
Very manual, very slow, very old-skool...but under the eyes of an experienced engineer the process could go quite fast (obvious false-starts and bad designs would not even be attempted) and leaves open the door of opportunity for something really innovative or new design breakthrough to transpire. (A eureka moment that leads to a new truss-hinge or some such being developed)
This is also analogous to having programming experts who program in machine language rather than programming in C+ and relying on software compilers.
The alternative (in designing the bridge) is to put your resources into hiring expert software programmers who build very smart search-optimization algorithms in which the engineer simply lists the design criteria (load, span, budget, preferred materials, etc) and presses a button in the program...the program then launches into a process of designing bridges, perhaps thousands of proto-types per second, and rank-sorts them by the engineers preferences and continues optimizing and tweaking them until either a local or global maximum/minimum is found in the genetic/AI algorithm.
Similar to software compilers as well.
That is kind of what a synthesized IC is like. Crudely, but I think the basic premise gets communicated here.
The problem right now with synthesis tools is no different than the challenges with automated bridge design or software compilers - the burden of being savvy and crafty shifts from the engineers (civil engineers for bridges, layout engineers for IC design) to the software programmers who must now figure out ways to avoid having their programs get hung up on local minima/maxima while at the same time incorporating some level of capability for capturing risk and critical flaws in the designs (which will become tangled messes of spaghetti noodles that no human will be able to debug or verify should things fail to work our properly once the bridge is built or the IC is coming out of the fab).
This is why I say a behemoth the likes of Intel, which already has a functioning and professionally polished internal process for robustly capturing the engineering care-abouts in their software (they do it for both their compilers as well as their computational lithography, not to mention TCAD) would really bring synthesis to a whole new level of capability and functionality.
Too basic? Not basic enough? Analogies suck because I included the mere mention of the possibility of a car being involved (load on the bridge)? Let me know if any of the above fleshed out the situation any better for you guys.