Intel's 10nm 'Cannon Lake' Processors Won't Arrive Until Late 2019 (digitaltrends.com)

At the company's second quarter 2018 financial results conference call, Intel chief engineering officer Venkata Renduchintala said the "Cannon Lake" 10mn processors won't appear in products until the 2019 holiday season. "The systems on shelves that we expect in holiday 2019 will be client systems, with data center products to follow shortly after," Renduchintala said. Interim CEO Robert Swan went on to tout the company's "very good lineup" of 14nm products. Digital Trends reports: "Recall that 10nm strives for a very aggressive density improvement target beyond 14nm, almost 2.7x scaling," Renduchintala said during the call. "And really, the challenges that we're facing on 10nm is delivering on all the revolutionary modules that ultimately deliver on that program." Although he acknowledged that pushing back 10nm presents a "risk and a degree of delay" in the company's road map, Intel is quite pleased with the "resiliency" of its 14nm roadmap. He said the company delivered an excess of 70 percent performance improvement over the last few years. Meanwhile, Intel's 10nm process should be in an ideal state to mass produce chips towards the end of 2019.

Intel's Cannon Lake chip is essentially a shrink of its seventh-generation "Kaby Lake" processor design. Given the previous launch window, the resulting chips presumably fell under the company's eighth-generation banner despite the older design. But with mass production pushed back to late 2019, the 10nm chips will fall under Intel's ninth-generation umbrella along with CPUs based on its upcoming "Ice Lake" design. Intel claims that its 10nm chips will provide 25 percent increased performance over their 14nm counterparts. Even more, they will supposedly consume 50 percent less power than their 14nm counterparts.

Comments

Re:Won't fix this decade, if ever

[Kjella]

That fundamental issues won't be changed in the next ten years, if ever.

Meltdown is a fairly simple hardware fix that AMD had already done right, don't speculate with memory that belongs to a different process. Intel fucked up big there but once the fix is in it's not likely to resurface. The Spectre class of exploits is tough but it's fairly trivially solved through software design - don't put secrets in the same process space as untrusted code like say Javascript you download online and there'll be nothing to steal even if you find a new side effect. That's the direction Chrome is going with Site Isolation and is pretty much a blanket protection for web browsing. It's still a big deal for cloud services etc. but if you'd rather be safe than sorry then run your own dedicated servers with just your code. Which is probably a good idea for all sorts of reasons if it's that sensitive.