Slashdot Mirror
Nvidia Is Trying To Make an x86 Chip
Slatterz writes with a story from PC Authority which says that "Word has reached us that Nvidia is definitely
working on an x86 chip and the firm is heavily recruiting x86 engineers all over Silicon Valley. The history behind this can be summarised by saying they bought an x86 team, and don't have a licence to make the parts. Given that the firm burned about every bridge imaginable with the two companies who can give them licences, Nvidia has about a zero chance of getting one."
how does pcauthority.com.au get away with re-posting others articles without even linking back to the original source (yes, I know that they credit theinquirer.net at the top, however it just links to all articles stolen from theinquirer.net).
No, the author is Charlie Demerjian from The Inquirer. Some years ago Charlie broke a NDA, so nVidia has removed him from the pool of journalists given notice of new releases. Since then Charlie writes only negative things ("they are broke", "they produce only faulty chips", "ATI is much faster", "CUDA stinks", "3D glasses are no good", etc. etc.) about nVidia. I've a spam filter about "news" about nVidia by Charlie (it's a pity slashdot reports this junk...)
They may have the base architecture available, but not any of the fancy simd or 64-bit instruction sets.
First appearances (not necessarily patent dates):
MMX - 1997
3DNow! - 1998
SSE - 1999
SSE2 - 2001
AMD 64 - 2003
Intel 64 - 2004
SSE3 - 2004
SSE4 - 2006
Of course, most software doesn't use any of these extensions, but Intel and AMD can use this as a weapon in a possible FUD campaign.
Back in the day, many purchasers demanded that manufacturers of electronics had a secound source of components so you wouldn't get stuck with a product line you could no longer build. AMD was Intel's second source provider. This agreement went to court http://findarticles.com/p/articles/mi_m0EKF/is_n1961_v39/ai_13734404 and the result was a forced agreement that meant AMD had access to Intel intel.
There are places where the networks are not touching,and there are places where they are-Boeing's Lori Gunter
No, the above post really overstates what goes on inside today's x86 chips.
It is true that Intel and AMD internally break up x86 into simpler "micro-ops" to simplify the internals of the chip. However, the specific micro-ops uses are tailored explicitly for x86 instructions, and many match up with x86 instructions one-to-one. The mapping really isn't that programmable, either. Most of the mapping is hard-coded and highly optimized. It would not be trivial to support another ISA such as PowerPC, even for just user-mode instructions. If you then consider all the privileged instructions, virtual memory, and virtualization stuff, you have a real mess. It would likely be easier to start from scratch rather than try to retrofit a current x86 to be anything other than an x86. Sure, you could reuse some of the arithmetic units and memory controllers perhaps, but the core would have to change pretty dramatically.
That said, Transmeta (RIP) did have technology that would likely make it easier to run non-x86 code on its processor, and the translation was done in software. But even its internal instructions were likely closely match to specifics of the x86 ISA.