We’ve talked about the hole in ARM’s product lineup for quite a while now. The Cortex A9 is too slow to compete with the likes of Intel’s Atom and Qualcomm’s Krait 200/300 based SoCs. The Cortex A15 on the other hand outperforms both of those solutions, but at considerably higher power and die area requirements. The slide below from Samsung illustrates my point clearly:



The comparison point here is the Cortex A15 and Cortex A7, but the latter should be quite performance competitive with a Cortex A9 so the comparison is still relevant. The Cortex A15 island in Samsung’s Exynos 5 Octa occupies 5x the die area as the A7 island, and consumes nearly 6x the power. In exchange for 5x the area and 6x the performance, the Cortex A15 offers under 4x the performance. It’s not exactly an area or power efficient solution, but a great option for anyone looking to push the performance envelope.


Today, ARM is addressing that hole with the Cortex A12.



This announcement isn’t a deep architectural disclosure, but we do have some high level details to share. Like AMD’s Jaguar, Intel’s Silvermont and even ARM’s A9, the Cortex A12 is a dual-issue out-of-order architecture. Unlike the Cortex A9, the Cortex A12 is fully out-of-order including the NEON/FP units (NEON/FP was in-order on Cortex A9).


Pipeline length increased a bit compared to Cortex A9 (11 stages), however ARM told me to expect similar frequencies to what we have with the Cortex A9. 


The execution back end has also been improved, although I don’t have many details as to how. My guess is we should expect something a bit wider than Cortex A9 but not nearly as wide as Cortex A15.


Memory performance is much improved compared to Cortex A9 as well, which we’ve already demonstrated as a significant weak point in the A9 architecture.


All of the architectural enhancements are supposed to provide up to a 40% increase in performance (IPC) over Cortex A9 at the same frequency and process node. ARM isn’t talking power, other than to say that it can do the same workload at the same power as a Cortex A9. In order words, Cortex A12 should have higher power than Cortex A9 but faster execution reduces total energy consumed. With a higher max power we’ll see more dynamic range in power consumption, but just not nearly as much as with the Cortex A15. 


Cortex A12 also adds support for 40-bit memory addressability, an intermediate solution before we get to 64-bit ARMv8 based architectures. Finally, Cortex A12 features the same ACE bus interface as Cortex A7/A15 and can thus be used in big.LITTLE configurations with either core (but likely exclusively with the A7s). Given the lower power profile of Cortex A12, I'm not sure the complexity of doing a big.LITTLE implementation will be worth it though.



ARM expects the Cortex A12 to be used in mainstream smartphones and tablets where cost and power consumption are a bit more important. The design makes a lot of sense, the only downside is its launch timeframe. ARM expects to be sampling Cortex A12 in late 2014 with the first devices showing up in 2015. Update: ARM clarified that SoCs based on Cortex A12 would be shipping to device vendors in mid-2014, with devices shipping to consumers by late 2014 to early 2015. ARM has optimized Cortex A12 processor packs at both Global Foundries (28nm SLP) and TSMC (28nm HPM).

Comments Locked


View All Comments

  • Egg - Sunday, June 2, 2013 - link

    The text is tiny. Also...
    "In exchange for 5x the area and 6x the performance, the Cortex A15 offers under 4x the performance." what?
  • lmcd - Sunday, June 2, 2013 - link

    6x power.
  • 4lpha0ne - Monday, June 3, 2013 - link

    That is the typical scaling effect of complexity (look up Pollack's rule) and power (roughly cubic increase in power with linear increase in clock frequency). There's no free lunch. ;)
  • lmcd - Tuesday, June 4, 2013 - link

    You understand that I understand, right?
  • MrSpadge - Monday, June 3, 2013 - link

    Tiny text: welcome to the beauty of high ppi devices. We need even more pixels...
  • jbo5112 - Tuesday, July 16, 2013 - link

    Tiny text: welcome to the world of foolish people defining non-raster (non photo/movie) sizes in px, instead of something like pt, in, or cm that automatically scales.
  • A5 - Sunday, June 2, 2013 - link

    Interesting. Hopefully they are planning a process shrink on A15 before then to help with the power some.

    These time frames would also seem to leave a pretty big window open on the high-end for Intel and/or AMD if they can execute properly. We're expecting a rev of Silvermont and Jaguar next year too, correct?
  • twotwotwo - Monday, June 3, 2013 - link

    ARM doesn't set a process roadmap like Intel does--folks like TSMC, GlobalFoundries, and Samsung do the fabbing, so they determine what process they'll introduce and when.

    Not to say ARM doesn't have a role optimizing for new processes as they come out; this story says they offered "optimized packages" for a couple of today's processes (though not Samsung's--Samsung might optimize for their own proc). They're just not driving the process (ha!) as Intel does.
  • Krysto - Monday, June 3, 2013 - link

    We should see Cortex A15 at 20nm next year (probably in Tegra 5, and Exynos 6), and then Cortex A57 at 14nm in 2015.
  • TheJian - Tuesday, June 4, 2013 - link

    Yes, so I don't understand the point of this chip for xmas 2014/2015Q1 devices. I will want a T5/Mali678/A340/rogue7 (whatever all these & more will be named) etc etc at 20nm by then. I guess this will be for feature phones by then :) I will expect much more from a smart device at xmas 2014 (or after in 2015 even worse). This seems to be about the perf of a T4i but a year later (likely with better power - but what about a T5i next July which is surely coming for mainstream?) or am I missing something here? Devices in 2015? I'm confused. Power of a 2013 xmas mainstream device (t4i to me, which is aimed at $200 phones last I checked) but not until 2015. Umm....Ok....LOL. I may have to take back the power comment, both fabs mentioned are running these on 28nm? Ok, a T5i (or whatever) makes these pointless if on 20nm. Again, even more confused. What the heck is any 28nm chip good for in 2015 for mobile? I can see from reading some of the other posts I'm not the only one confused.

Log in

Don't have an account? Sign up now