Arm Community
Arm Community
  • Site
  • User
  • Site
  • Search
  • User
Arm Community blogs
Arm Community blogs
Architectures and Processors blog RISC versus CISC Wars in the PostPC Eras - Part 2
  • Blogs
  • Mentions
  • Sub-Groups
  • Tags
  • Jump...
  • Cancel
More blogs in Arm Community blogs
  • AI blog

  • Announcements

  • Architectures and Processors blog

  • Automotive blog

  • Embedded and Microcontrollers blog

  • Internet of Things (IoT) blog

  • Laptops and Desktops blog

  • Mobile, Graphics, and Gaming blog

  • Operating Systems blog

  • Servers and Cloud Computing blog

  • SoC Design and Simulation blog

  • Tools, Software and IDEs blog

Tell us what you think
Tags
Actions
  • RSS
  • More
  • Cancel
Related blog posts
Related forum threads

RISC versus CISC Wars in the PostPC Eras - Part 2

David Patterson
David Patterson
September 11, 2013
3 minute read time.

In my first blog, we examined gave the historical context of the instruction set battles of ARM and x86, covering the RISC-CISC Wars in the PrePC Era and the PC Era. This blog covers Round 3, the PostPC Era [1].

Round 3: RISC vs. CISC in the PostPC Era
The importance of maintaining the sequential programming model combined with the increasingly abundant number of transistors from Moore's Law led, in my view, to wretched excess in computer design. Measured by performance per transistor or by performance per watt, the designs of the late 1990s and early 2000s were some of the least efficient microprocessors ever built. This lavishness was acceptable for PCs, where binary compatibility was paramount and cost and battery life were less important, but performance was delivered more by brute force than by elegance.

However, these excessive designs are not a good match to the smartphones and tablets of the PostPC era. RISC dominates these "Personal Mobile Devices", because

  • It's a new software stack and software distribution is via the "App Store model" or the browser, which lessens the conventional obsession with binary compatibility.
  • RISC designs are more energy efficient.
  • RISC designs are smaller and thus cheaper.

The table below from Microprocessor Report supports these last two claims [2]:


Comparing performance per megahertz, x86 is 4% - 8% faster than ARM or MIPS. More significantly, this table suggests ARM and MIPS have 40% - 50% better energy per MHz and their size is a factor of 3X to 4X smaller than x86.

Independent of these architectural battles, Personal Mobile Devices rely on "Systems on a Chip" to reduce size, improve energy, and to lower costs. If processors are available as IP blocks, any company can create a single SOC rather than use many separate chips on a printed circuit board, as is the case with PCs. Thus far, there is no serious x86 IP competitor to the many fine RISC IP options, so SOCs based on x86 can only come from AMD or Intel.

RISC vs. CISC in the Client and in the Server of the PostPC Era
If Personal Mobile Devices are the clients of the PostPC Era, then Cloud Computing is the server. Virtually all PostPC apps will have one foot in the client and one in the cloud. While RISC has a substantial lead in PMDs, CISC leads in the commodity server market that is the building block of Cloud Computing. 

Interestingly, binary compatibility again plays a small role in Cloud Computing, and cost and energy efficiency again play a much larger role than in PCs. Moreover, when you acquire 100,000 servers at a time to build a Warehouse Scale Computer, custom microprocessors could make sense. RISC competitors would need 64-bit addresses, ECC-protected memory, and good virtual machine support to compete in the Cloud, but the door is not slammed shut as it was in the PC Era.

Conclusion: RISC Reascendancy for Round 3
Note that the volume is on the side of PMDs in the PostPC Era: there will surely be 100 chips built for PMDs for every chip made for Cloud Computing. For 2010, even if you include the whole PC market - which you would expect to fade eventually in the PostPC Era-the RISC chips still outnumber CISC chips by 10:1 to 15:1.

Depending on your perspective, a happy result of the latest round of the RISC-CISC Wars is RISC reascendancy.
_________________________________
[1] "Dawn of a New Day," Ray Ozzie, http://ozzie.net/doc...n-of-a-new-day/, October 28, 2010.
[2] "Broadcom Shows Off New CPU," Linley Gwennap, Microprocessor Report, November 22, 2010.

Anonymous
Parents
  • David Patterson
    David Patterson over 12 years ago
    While everyone is entitled to an opinion, what I like about computer architecture is that industry unintentionally experiments with controversial issues to help shed light on contrasting opinions.

        In addition to supplying the table that quantitatively compared many instruction sets that appeared in the last blog, Microprocessor Report recently published an article about the use of x86 based Atom processors in tablet computers, one of the PostPC personal devices that I talked about :

        "At IDF Beijing, Intel formally launched its Oak Trail processor for netbooks and tablets.  ... Oak Trail uses the second-generation Atom Z670 processor This single-core dual-thread CPU operates at 1.5GHz for Oak Trail, down from the 1.9GHz that Intel had originally specified for Moorestown, ... which gained no customers at all]. ... With dual threading, a 1.5GHz Oak Trail should deliver performance only slightly better than that of a dual-core 1.0GHz Cortex-A9 processor. These ARM processors are available today from several vendors at less than half the price, power, and board area of Oak Trail. Thus, we don't see Oak Trail as a credible tablet product unless Windows 7 compatibility is required. Windows 7 tablets, however, have sold relatively few units, mainly in industrial and vertical applications. Medfield [a successor to Oak Trail] may close the gap on power and price, but by the time it ships, dual- and quad-core ARM processors will in production at up to 1.5GHz, leaving no performance advantage for Intel."

                                                      Linley Gwennap, "In Brief: Oak Trail Leads Intel to Tablets," Microprocessor Report, May 2, 2011

        Since binary compatibility can't be used as an excuse to stick to an inefficient instruction set in PostPC devices, differences in power, price, and area seems a rational reason. Factors of two in power, price, AND board area help explain why there were 6.1B ARM devices sold in PostPC devices in 2010, a twentyfold increase over x86 designs.

        Computer architects I know believe that the  complicated and continuously expanding x86 instruction set--enhanced by one instruction per month since its introduction in 1978--is the technical reason behind the doubling of power, price, and area, and factors of two will matter for a long, long time.

    • Cancel
    • Up 0 Down
    • Reply
    • More
    • Cancel
Comment
  • David Patterson
    David Patterson over 12 years ago
    While everyone is entitled to an opinion, what I like about computer architecture is that industry unintentionally experiments with controversial issues to help shed light on contrasting opinions.

        In addition to supplying the table that quantitatively compared many instruction sets that appeared in the last blog, Microprocessor Report recently published an article about the use of x86 based Atom processors in tablet computers, one of the PostPC personal devices that I talked about :

        "At IDF Beijing, Intel formally launched its Oak Trail processor for netbooks and tablets.  ... Oak Trail uses the second-generation Atom Z670 processor This single-core dual-thread CPU operates at 1.5GHz for Oak Trail, down from the 1.9GHz that Intel had originally specified for Moorestown, ... which gained no customers at all]. ... With dual threading, a 1.5GHz Oak Trail should deliver performance only slightly better than that of a dual-core 1.0GHz Cortex-A9 processor. These ARM processors are available today from several vendors at less than half the price, power, and board area of Oak Trail. Thus, we don't see Oak Trail as a credible tablet product unless Windows 7 compatibility is required. Windows 7 tablets, however, have sold relatively few units, mainly in industrial and vertical applications. Medfield [a successor to Oak Trail] may close the gap on power and price, but by the time it ships, dual- and quad-core ARM processors will in production at up to 1.5GHz, leaving no performance advantage for Intel."

                                                      Linley Gwennap, "In Brief: Oak Trail Leads Intel to Tablets," Microprocessor Report, May 2, 2011

        Since binary compatibility can't be used as an excuse to stick to an inefficient instruction set in PostPC devices, differences in power, price, and area seems a rational reason. Factors of two in power, price, AND board area help explain why there were 6.1B ARM devices sold in PostPC devices in 2010, a twentyfold increase over x86 designs.

        Computer architects I know believe that the  complicated and continuously expanding x86 instruction set--enhanced by one instruction per month since its introduction in 1978--is the technical reason behind the doubling of power, price, and area, and factors of two will matter for a long, long time.

    • Cancel
    • Up 0 Down
    • Reply
    • More
    • Cancel
Children
No Data
Architectures and Processors blog
  • When a barrier does not block: The pitfalls of partial order

    Wathsala Vithanage
    Wathsala Vithanage
    Acquire fences aren’t always enough. See how LDAPR exposed unsafe interleavings and what we did to patch the problem.
    • September 15, 2025
  • Introducing GICv5: Scalable and secure interrupt management for Arm

    Christoffer Dall
    Christoffer Dall
    Introducing Arm GICv5: a scalable, hypervisor-free interrupt controller for modern multi-core systems with improved virtualization and real-time support.
    • April 28, 2025
  • Getting started with AARCHMRS Features.json using Python

    Joh
    Joh
    A high-level introduction to the Arm Architecture Machine Readable Specification (AARCHMRS) Features.json with some examples to interpret and start to work with the available data using Python.
    • April 8, 2025