Since this small core needs to be a more power saving core than the big core sibling, A75. I would imagine they retain the in-order execution for the upcoming A55.Wondering if A55 is out of order like A57 and A72 or in order like A35 or A53...
Since this small core needs to be a more power saving core than the big core sibling, A75. I would imagine they retain the in-order execution for the upcoming A55.Wondering if A55 is out of order like A57 and A72 or in order like A35 or A53...
I say that because there is the ARM A35 as the in order core... and A55 seems more like a more power efficient A57...Since this small core needs to be a more power saving core than the big core sibling, A75. I would imagine they retain the in-order execution for the upcoming A55.
Only architectures released from now are compatible with the new DynamIQ, so you can't mix A75+A35 ( i read that in ARM web ). And there is a big gap in performance between A55 and A57 they have nothing in common, it is designed for effiency at low tasks.I say that because there is the ARM A35 as the in order core... and A55 seems more like a more power efficient A57...
Ok.. so A35 ended to be a failed core? Time for a rework for them?Only architectures released from now are compatible with the new DynamIQ, so you can't mix A75+A35 ( i read that in ARM web ). And there is a big gap in performance between A55 and A57 they have nothing in common, it is designed for effiency at low tasks.
No, it was a improved version of Cortex A7 with 64bit support. Actually it is supposed to be a bit more efficient compared to A53 at the cost of some perfomance lost.Ok.. so A35 ended to be a failed core? Time for a rework for them?
From what i know, ARM decided to have three different envelopes for their cortex core: Ultra high efficiency, high efficiency and high performance.I say that because there is the ARM A35 as the in order core... and A55 seems more like a more power efficient A57...
But... Was is supposed to be compatible with the higher tier cores like the A7?No, it was a improved version of Cortex A7 with 64bit support. Actually it is supposed to be a bit more efficient compared to A53 at the cost of some perfomance lost.
Actually the A32 is there for you said. It even doesn't need to be at 64 bit.The A35 target usage is as a ultra low cost and power core in embedded, IoT and ultra low cost. It doesn't need to be in a BL design.
Disregarding DynamiQ interoperability, the new cores are simply incompatible with the old ones since they're ARMv8.2.
Thanks for the link.Found a live feed for ARM's Computex event (already started) https://www.youtube.com/watch?v=ClCVaBkIgPk
The new cores (A75 and A55) will not work with the older cores in a big.LITTLE configuration. It will only works between them (A75 + A55).But... Was is supposed to be compatible with the higher tier cores like the A7?
I guess that someone must ask for them on the official presentation.
If is compatible it would mark the end of big.LITTLE and mark the beginning of the Cluster designs.
That's because it would be a big incoherency from ARM to leave the low power core outside this array and it would not improve more than expecting.
Ok, it is confirmed by today... So A35 can be easily done now since A55 can be downscale as well.The new cores (A75 and A55) will not work with the older cores in a big.LITTLE configuration. It will only works between them (A75 + A55).
What?Apple's WWDC conference keynote is on Monday; and they are expected to announce the A10X (?) iPad Pro. Unsure if it will be TSMC 10 nm or not.
Don't know if it will really hit the ~4200 ST GB4 score rumored a couple months ago, but that would be nice.
What?
This one?
Would there any news from Intel or x86? Any hope to see new x86 mobile chips?
Ive see the Win10 thing on SD835, but im just not sure, they avoided any kind of perf show, not sure about how good the part of x86 bin to ARM will work(and with what instruction support), in teory is the same system used to run x86 on Itanium, and the no x64 bin support is a big letdown.
Currently even some SW doesn't work on x86 at all due Idiot Programming on their finnest... Specially some games like MapleStory since even on a Haswell chip it crashes like nothing....I would not expect x86 games to work at all if that is what you are asking. Probably more like Office and other light productivity apps (although I would have to think MS would recompile Office to ARM)
I bet Xiaomi would love to have this chip in some their other phones (other than their Mi 6C). Perhaps it would end up in Redmi Note 5?New news from the web...
https://www.gizmochina.com/2017/06/03/snapdragon-660-powered-oppo-r11
CPU wise it happened again... The new generation is defeating the old one... Kryo barely wins in Single Thread here due their FP performance. However on Multi Thread the massacre is done.
Meanwhile, is pending to see how the GPU was improved and how near they are from Adreno 530 or even if they defeated the Adreno 430.
Indeed. It will end on the Global Version of the Redmi Note 5I bet Xiaomi would love to have this chip in some their other phones (other than their Mi 6C). Perhaps it would end up in Redmi Note 5?
I'm looking forward to seeing more of ARM new form of netbook. I might actually buy one after a few generations down the line.Ive see the Win10 thing on SD835, but im just not sure, they avoided any kind of perf show, not sure about how good the part of x86 bin to ARM will work(and with what instruction support), in teory is the same system used to run x86 on Itanium, and the no x64 bin support is a big letdown.
Also the SD835 supports DX9/11??? it says DX12/Vulkan/ES 3.0.