If you are still running an outdated os like Android 6.0.1, is there any option to patch against Meltdown and Spectre other than moving to the latest Android versions?
The nexus 5 is no longer supported by Google so even moving to the latest available andriod version isn't going to help you. Maybe Google will provide a patch for older devices but I wouldn't hold my breath.
Sent from my [device_name] using XDA-Developers Legacy app
Thanks. So the only remaining option is buying a new phone. Had to happen sooner or later.
Now comes the dilemma of deciding which one to get ..... or just ignoring the threat since I'm not likely to be a target of the nsa or similar caliber hackers.
maybeme2 said:
Thanks. So the only remaining option is buying a new phone. Had to happen sooner or later.
Now comes the dilemma of deciding which one to get ..... or just ignoring the threat since I'm not likely to be a target of the nsa or similar caliber hackers.
Click to expand...
Click to collapse
The risk to an android device is very low according to Google. If that helps you decide on a course forward.
Sent from my [device_name] using XDA-Developers Legacy app
i dont think our cpus at risk, we dont have any Cortex cores which are spectre risks(Cortex-A75, Cortex-A73, Cortex-A72, Cortex-A57-, Cortex-A17, and Cortex-A9). we have Krait 400 cores.
TheIronLefty said:
i dont think our cpus at risk, we dont have any Cortex cores which are spectre risks(Cortex-A75, Cortex-A73, Cortex-A72, Cortex-A57-, Cortex-A17, and Cortex-A9). we have Krait 400 cores.
Click to expand...
Click to collapse
Well that is good to know.
Thanks.
TheIronLefty said:
i dont think our cpus at risk, we dont have any Cortex cores which are spectre risks(Cortex-A75, Cortex-A73, Cortex-A72, Cortex-A57-, Cortex-A17, and Cortex-A9). we have Krait 400 cores.
Click to expand...
Click to collapse
Looks like Qualcomm just admitted that they are exposed [ref1]. They won't name which chipsets or which CPUs in those chipsets are affected. It's my understanding that Krait has speculative [ref3] execution and was designed as a clone of Cortex-A15, which is affected by spectre [ref2]. So to summarize my opinion:
Vunerabilities
Meltdown : No
Spectre: Possibly
ref1: https://www.theregister.co.uk/2018/01/06/qualcomm_processor_security_vulnerabilities/
ref2: https://developer.arm.com/support/security-update
ref3: https://forum.fairphone.com/t/fp2-patch-for-meltdown-spectre/36754/4
Related
SammyHub said:
Samsung has just unveiled a new System-on-chip (SoC) for future mobile devices. It’s the Exynos 5250 that boasts two Cortex-A15 chips clocked at 2GHz. The dual-core Exynos 5250 is created using a 32nm-low power HKMG process and is said to double the performance when compared to a 1.5GHz dual-core SoC based on Cortex-A9.
In addition to improved processing performance, Exynos 5250 features graphics performance improved by four times compared to Cortex-A9-based Application Processors, supports stereoscopic 3D displays and a display resolution of up to WQXGA (2560×1600).
Samsung says the new Exynos chip will be used in high-end tablets and will be mass produced sometime in the second quarter of next year.
Click to expand...
Click to collapse
http://sammyhub.com/2011/11/30/samsung-unveils-cortex-a15-2ghz-exynos-5250-soc/
I have a feeling this will run circles around Tegra 3.
Killer Bee said:
http://sammyhub.com/2011/11/30/samsung-unveils-cortex-a15-2ghz-exynos-5250-soc/
I have a feeling this will run circles around Tegra 3.
Click to expand...
Click to collapse
Damn, I just posted it in the Galaxy S3 rumor page.
Yea, you are right. It will run circles and a few squares and rectangles around any A9 SoC.
4x the Mali-400MP eh, I guess that means a new GPU. I wonder which one since the Mali-T604 won't be out until 2013.
Could be S3 material, the timing (Q2) matches.
Perhaps the GPU is the SGX543's successor ?
a strong mobile and i will have a buy ..
Initially this SoC will be available to Galaxy series Tablets and not for Smartphones.....
Killer Bee said:
4x the Mali-400MP eh, I guess that means a new GPU. I wonder which one since the Mali-T604 won't be out until 2013.
Click to expand...
Click to collapse
T604 & T658 will arrive next year in devices according to this blog...
http://blogs.arm.com/multimedia/626-launching-mali-t658-“hi-five-eight-welcome-to-the-party”/
Nigma2k said:
T604 & T658 will arrive next year in devices according to this blog...
http://blogs.arm.com/multimedia/626-launching-mali-t658-“hi-five-eight-welcome-to-the-party”/
Click to expand...
Click to collapse
I'd like the T604 to be in the Exynos 5250 but that gpu was said to be 10x more powerful than the Mali-400, something Samsung would probably state if that was were the case.
Sent from my HTC Vivid™
nice, maybe i will buy it
I'm thinking a Mali T604 in the 4412 and SGX 543 MP4 in the 5520. They recently announced that they have a license for 5 series MP
Killer Bee said:
I'd like the T604 to be in the Exynos 5250 but that gpu was said to be 10x more powerful than the Mali-400, something Samsung would probably state if that was were the case.
Sent from my HTC Vivid™
Click to expand...
Click to collapse
T658 will be 10x Mali 400, so t604 is more inline with what Samsung are saying.
iPad 3 with A5 S? It's been mention it'll have a higher resolution and it's been mentioned that its coming soon.
Put one in a galaxy tab and give me some xda devs making firmware for it and i'll get it.
The Dogan said:
iPad 3 with A5 S? It's been mention it'll have a higher resolution and it's been mentioned that its coming soon.
Click to expand...
Click to collapse
Who made the processor ? Samsung ? I don't think so
Sent from my GT-S5830 using XDA App
thats gonna be a crazy phone
EmoBoiix3 said:
Who made the processor ? Samsung ? I don't think so
Sent from my GT-S5830 using XDA App
Click to expand...
Click to collapse
I thought it was based on theirs? Just with some tweaks for iOS and all that.
EDIT: Just checked wikipedia and it says the A5 is manufactured by Samsung. If it's manufactured by sammy then I'd say there's a pretty good chance it's based on their tech.
No its actually apple that designed it and sent the blueprints to SAMSUNG to make.
$1 gets you a reply
Looks really nice, thanks!
Kailkti said:
No its actually apple that designed it and sent the blueprints to SAMSUNG to make.
$1 gets you a reply
Click to expand...
Click to collapse
Aren't they at war ?
Sent from my GT-S5830 using XDA App
I wonder how much it will overclock
Yes I've used the search tool and the last post in the last Exynos 5250 thread was at december 2011 and I can't find any rules about reviving old threads so I don't want to fiddle with it since I might get an infraction or worse a ban and and the last Tegra 4 thread wasn't coherent enough for me.
I don't know all the details but I would like to start talking about the supposed new Exynos 5250 and Tegra 4 development so please bear with me, I need all of those who has reliable information to add in the discussion. I'd like to start things with how will it fare against this year's smartphones and tablets? specifically the Samsung Galaxy S3 (1.4 ghz Quad ARM Cortex-A9 + Exynos 4412 & 1.5 GHz dual-core Qualcomm Krait + Snapdragon S4 MSM8960) and HTC one X ( 1.5 GHz quad-core ARM Cortex-A9 + Nvidia Tegra 3 & 1.5 GHz dual-core Qualcomm Krait + Snapdragon S4 MSM8960) since they are currently the top Phones out there in the market performance wise.
Further into the topic will the new Exynos and Tegra make their predecessors completely obsolete once they come out? or is the performance leap going to be minimal at best? due to various factors perhaps you can't fully utilize their potential due to the limiting software apps out there? What I want you guys to elaborate for the community is how better will it be in terms of CPU and GPU benchmark performance. Please do share your Ideas and any reliable information about the said topic at hand.
P.S. I just got an SGS3 my very first smartphone and android, did I make a huge mistake by buying it or should have I gone for a cheaper Galaxy Nexus and waited for the new Exynos to come out?
Itadakiimasu said:
Yes I've used the search tool and the last post in the last Exynos 5250 thread was at december 2011 and I can't find any rules about reviving old threads so I don't want to fiddle with it since I might get an infraction or worse a ban and and the last Tegra 4 thread wasn't coherent enough for me.
I don't know all the details but I would like to start talking about the supposed new Exynos 5250 and Tegra 4 development so please bear with me, I need all of those who has reliable information to add in the discussion. I'd like to start things with how will it fare against this year's smartphones and tablets? specifically the Samsung Galaxy S3 (1.4 ghz Quad ARM Cortex-A9 + Exynos 4412 & 1.5 GHz dual-core Qualcomm Krait + Snapdragon S4 MSM8960) and HTC one X ( 1.5 GHz quad-core ARM Cortex-A9 + Nvidia Tegra 3 & 1.5 GHz dual-core Qualcomm Krait + Snapdragon S4 MSM8960) since they are currently the top Phones out there in the market performance wise.
Further into the topic will the new Exynos and Tegra make their predecessors completely obsolete once they come out? or is the performance leap going to be minimal at best? due to various factors perhaps you can't fully utilize their potential due to the limiting software apps out there? What I want you guys to elaborate for the community is how better will it be in terms of CPU and GPU benchmark performance. Please do share your Ideas and any reliable information about the said topic at hand.
P.S. I just got an SGS3 my very first smartphone and android, did I make a huge mistake by buying it or should have I gone for a cheaper Galaxy Nexus and waited for the new Exynos to come out?
Click to expand...
Click to collapse
what better than Nvidia Tegra 3
First off, let's talk processors:
Your phone, the SGS3 i9300 is packing the Quad-Core Exynos 4412, rather than the dual-core Snapdragon S4 (MSM8960) for North American versions of the SGS3. The international version of the HTC One X has the 1.5GHz Tegra 3 vs the North American version which has the S4 as well.
Performance wise, these processors are all pretty on-par. Benchmark scores are close, with the Tegra 3 gaining the upper hand graphics-wise with its 12-core GPU. The processor to look out out of these 3 would be the S4, considering it's the first processor to (kinda) take advantage of the A15 cortex.
...The reason I say kind of, is because there is some discussion on the S4 being a hybrid between the A9 cortex (Tegra 3, Exynos 4) and the beastly A15. Qualcomm is a rebel, and doesn't follow ARM's chip designs like the others do. But I digress...
A15 is going to be a HUGE improvement over A9. HUGE performance gains, higher resolution displays, USB 3.0,OpenGL ES 3.0 (depending on the GPU) and much much more. The dual-core Exynos 5250 is going to be based off the A15 cortex, and it's going to blow even the quad core A9's out of the water. Tegra 4 will almost definitely be based off A15 as well, and it's going to be a sight to see. As for the Snapragon S5, who knows? I'm sure Qualcomm has some cool stuff up it's sleeve.
To answer your question, yes the new Exynos and Tegra processors are going to make older generation processors obsolete, but that doesn't mean you made a bad choice. The SGS3 is a great phone, and as such has tons of developers making custom roms, kernals, and other fun hacks to keep you occupied for the months to come hack away!
hope that helped!
You didn't make a mistake as at present android is not able to push current quadcore devices to their limits and there is a scope for lot more improvement
So even though next gen processors will be lot more powerful, your phone will still be able to handle next android releases so Don't worry and enjoy your S3
Sent from my HTC One X using xda app-developers app
vivek_bhoj said:
You didn't make a mistake as at present android is not able to push current quadcore devices to their limits and there is a scope for lot more improvement
So even though next gen processors will be lot more powerful, your phone will still be able to handle next android releases so Don't worry and enjoy your S3
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Android already has full multi core support. The only thing holding back multi cores is the fact that many apps still don't make use of them.
Also, that other guy made some great points but forgot to mention S4 Pro, which we already know a good deal about and is very impressive. It sets the bar high for the next tegra and for exynos 5250.
Sent from my HTC Sensation 4G using xda app-developers app
Itadakiimasu said:
Further into the topic will the new Exynos and Tegra make their predecessors completely obsolete once they come out? or is the performance leap going to be minimal at best?
Click to expand...
Click to collapse
They're not going to be "completely obsolete" (even GN and SG2, for example, are still good phones despite being "last year") but there is going to be a large performance increase to A15.
There's always a next big thing coming out, but generally it's not worth waiting for unless you're on the cusp. Even if the generation you shop is relatively old, the competitive market (unlike, say, that of a fruity company) helps to compensate you by providing discounts of the previous tech.
S3, in particular, is a darn good phone no matter how you look at it (except that it has hardware buttons, but I digress..)
So I got my i9500 and already did some foolery with it.
Fine device, but I hate the raised lip around the screen edge. Something I definitely did not miss on the S3 and something very annoying.
Other than that small design critique:
THE ****ING PHONE ISN'T RUNNING FINAL FIRMWARE!
Basically the CPU is running on the cluster migration driver, meaning it switches all four cores from the LITTLE to the big cluster, as opposed to the core migration driver who does this in an individual core-pair manner.
You can pretty much throw all battery comparisons out of the window: it's completely unfinished and unoptimal.
I already compiled the kernel and flashed it without the cluster migration tidbit, but the phone won't boot. So yea. Current sources also useless.
Cleverly enough: you can't really distinguish between the two drivers apart from one manner: if /sys/devices/system/cpu/cpufreq/iks-cpufreq/max_eagle_count is present, you're running an IKS driver. If it's not, then you're running the sub-optimal IKCS driver.
So yea. We'll see what Samsung does about this, currently the advantages of big.LITTLE are pretty much unused.
Another nail in the coffin on how rushed and unprepared this phone has been.
Wow, this is seriously turning out to be a fiasco.
ChronoReverse said:
Wow, this is seriously turning out to be a fiasco.
Click to expand...
Click to collapse
This is EXACTLY why at the end I don't care for technical details about socs but was rather waiting for real world usage first. As much I wanted to agree with Andrei Lux on how intelligent BigLittle is, I sort of felt that it wont be same at the end.
Question is now: Is this possible to fix in the near future?? So that maybe buying the Exynos will be beneficial if the devs take over. I wont bet on Samsung introducing mind-blowing improvements in that department in upcoming firmwares
Xdenwarrior said:
Question is now: Is this possible to fix in the near future?? So that maybe buying the Exynos will be beneficial if the devs take over. I wont bet on Samsung introducing mind-blowing improvements in that department in upcoming firmwares
Click to expand...
Click to collapse
The code other driver is there in the kernel, it's just not used. No idea. It's not like we need Samsung for it: I already talked to a developer at Linaro about some incomplete switcher code that's being currently getting the green-light to be made public. But who knows how long that will take.
Whatever the case, I gather that they can't just let it be in the current state.
AndreiLux said:
The code other driver is there in the kernel, it's just not used. No idea. It's not like we need Samsung for it: I already talked to a developer at Linaro about some incomplete switcher code that's being currently getting the green-light to be made public. But who knows how long that will take.
Whatever the case, I gather that they can't just let it be in the current state.
Click to expand...
Click to collapse
Any way to just disable cortex a15 altogether yet just to see how well cortex a7 will perform in simple texting, browsing, calling and to see what the battery life will be like on that?? (cause cortex a7 only uses like 200 something mw as opposed to 1000mw for snapdragon). I know u wont be able to game. How often does Cortex A15 hits in? cause I would suspect a much worse battery life with incomplete drivers doing the switching if its very often on. But PocketNow reports very similar battery results to snapdragon variant which I find odd
Xdenwarrior said:
Any way to just disable cortex a15 altogether yet just to see how well cortex a7 will perform in simple texting, browsing, calling and to see what the battery life will be like on that?? (cause cortex a7 only uses like 200 something mw as opposed to 1000mw for snapdragon). I know u wont be able to game. How often does Cortex A15 hits in? cause I would suspect a much worse battery life with incomplete drivers doing the switching if its very often on. But PocketNow reports very similar battery results to snapdragon variant which I find odd
Click to expand...
Click to collapse
Use any app to limit the CPU frequency to 600MHz. That'll limit it to the A7 cores running to 1200MHz. Basically you can just use CPU-Spy. Everything <= 600 are A7's mapped at half frequency, everything above it are A15's at 1:1 frequency.
As for PocketNow: irrelevant. The difference is what could be instead of what is, the Snapdragon doesn't play a role in the discussion here.
WOW , thats sucks
Samsung was too rushed and ruined it :/
AndreiLux said:
Use any app to limit the CPU frequency to 600MHz. That'll limit it to the A7 cores running to 1200MHz. Basically you can just use CPU-Spy. Everything <= 600 are A7's mapped at half frequency, everything above it are A15's at 1:1 frequency.
As for PocketNow: irrelevant. The difference is what could be instead of what is, the Snapdragon doesn't play a role in the discussion here.
Click to expand...
Click to collapse
Hey thanks, but I don't have the S4 to test it with since i'm still debating on which to get. I live in Canada and so the only version here which I can get a lot cheaper on a contract is LTE snapdragon, but I wont mind getting the Exynos since it got potential. Besides 16GB internal isn't enough for me. So that's why asking if u seen any improvements in battery when only cortex a7 ran? If a7 doesn't do much in power consumption, then no point spending 800 bucks and loosing LTE altogether...
@bala_gamer please see my PM its important...
Sent from my GT-I9500 using xda premium
Oh wow. Just got word (without further in-depth explanation) that this might actually be a hardware limitation. Coming from a reliable source.
No words...
AndreiLux said:
Oh wow. Just got word (without further in-depth explanation) that this might actually be a hardware limitation. Coming from a reliable source.
No words...
Click to expand...
Click to collapse
Can you elaborate a bit more pls?
Sent from my GT-I9500 using Tapatalk 2
that's not what samsung exynos advertised..
http://www.youtube.com/watch?v=U6UNODPHAHo
Is it possible that we're having a simpler Exynos 5 system technically closer to Exynis 5 Quad (plus 4 A7 cores) than a real seamless Octa-core system? It was strange reading that "Octa-core manufacturing starts in Q2" (April-June) then see Octa-core versions hitting reviewers early April, that's way too low time frame. Maybe this is a 1st-gen 5410. In any case, performance and current-state battery life beats the Snapdragon version, even if only just.
AndreiLux said:
Basically the CPU is running on the cluster migration driver,
Click to expand...
Click to collapse
wtf? Well done Samsung... This is ridiculous...
AndreiLux said:
Oh wow. Just got word (without further in-depth explanation) that this might actually be a hardware limitation. Coming from a reliable source.
No words...
Click to expand...
Click to collapse
WHAT THE [email protected]??!!
Actually WTF is a massive understatement here....!!!
Please can you give more info about this matter whenever is possible? This is very serious...
Is it a specific hardware limitation? Something that Samsung specificly did in GS4 (I9500) ?
Because this can't be a generic exynos octa limitation. It makes no sense... Unless everything we've read from Samsung and ARM about exynos octa, are completely misleading...
A hardware limitation..? They advertised the functionality and to then release a device without it, is just plain stupid. Hopefully it is a just a kernel issue and can be resolved quickly.
Sent from my Galaxy Nexus using xda premium
Probably Samsung will implement it in their Note 3 device? It's a conspiracy so that people buy their next Note phone but this news is sad.
Sent from my GT-I9100 using Tapatalk 2
Now what is this all about? Is this a very serious issue?
So its either all A15s or all A7s?
so would the 'octa' really be a better choice than the S600? That should be powerful enough.. and the S600 is pretty power efficient too
rkial said:
So its either all A15s or all A7s?
so would the 'octa' really be a better choice than the S600? That should be powerful enough.. and the S600 is pretty power efficient too
Click to expand...
Click to collapse
What I understood is its either the full cluster of a7 or a15 is used/ functional based on the load, dynamically turning on one or two cores of a15 to work along with a7 may not be possible it seems.
I may be wrong, waiting for an elaborate exp from andrei
Sent from my GT-I9500 using Tapatalk 2
bala_gamer said:
What I understood is its either the full cluster of a7 or a15 is used functional based on the load, dynamically turning on one or two cores of a15 to work along with a7 may not be possible it seems.
I may be wrong, waiting for an elaborate exp from andrei
Sent from my GT-I9500 using Tapatalk 2
Click to expand...
Click to collapse
I was always under the impression this was the intention of Samsung's particular implementation of it. I thought it was common knowledge that Samsung's version worked on a 4 or 4 (A15) or (A7) basis.
Maybe he was talking about the ability to change that.
Sad News:
Sammy exec confirmed this:
http://www.gsmarena.com/samsung_galaxy_s4_and_note_3_wont_get_true_octacore_update-news-6908.php
No wonder that they released videos of hmp on 5420 instead of note 3.
http://www.youtube.com/watch?v=Zwbeb08W27U&feature=youtu.be&ism=SASep1513Facebook1
This is cheating but still that is not going to affect my descision to buy note3.
What do u guys think?
Yet people are still buying and will be buying samsung devices.
Oh noez, no 8 cores in your phone? How will we survive? Seriously, at some point cores will become ubiquitous, nobody will really care once the OS and software just uses available resources. We're getting closer, but I doubt your phone is doing anything that'd really require 8 cores to do.
khaytsus said:
Oh noez, no 8 cores in your phone? How will we survive? Seriously, at some point cores will become ubiquitous, nobody will really care once the OS and software just uses available resources. We're getting closer, but I doubt your phone is doing anything that'd really require 8 cores to do.
Click to expand...
Click to collapse
Well HMP/GTS is not jus running all 8 cores at a time its about firing up the required number of cores in any combination of a7's and a15's currently afaik it cluster migration ( the worst implimation of big.littile).
jsriz said:
Well HMP/GTS is not jus running all 8 cores at a time its about firing up the required number of cores in any combination of a7's and a15's currently afaik it cluster migration ( the worst implimation of big.littile).
Click to expand...
Click to collapse
I think Note 3 is running core migration, which is much better than cluster migration.
system.img said:
I think Note 3 is running core migration, which is much better than cluster migration.
Click to expand...
Click to collapse
Wrong.Note 3 came with cluster migration.
The Note 3 is still running cluster migration and I'll doubt this will change anytime soon. Their drivers are still out of date for normal IKS so I won't even bother trying to get that running on a device I don't own. And frankly nobody else is interested in doing the work.
Click to expand...
Click to collapse
ff - sorry can't delete
Mod Edit
Duplicate thread is closed
Original is HERE
malybru
Forum Moderator
so i saw that the apple a7 chip is actually just a snapdragon 800 processor just like our nexus 5, does that mean the nexus 5 kernel does support 64bit?
Toxina said:
so i saw that the apple a7 chip is actually just a snapdragon 800 processor just like our nexus 5, does that mean the nexus 5 kernel does support 64bit?
Click to expand...
Click to collapse
No, it doesnt. The entire system has to be optimised for 64-bit and not only the chip.
gee2012 said:
No, it doesnt. The entire system has to be optimised for 64-bit and not only the chip.
Click to expand...
Click to collapse
Android wouldn't really need to be optimized for 64-bit like the iPhone 5s because Android uses a virtual machine (Dalvik) to run apps, whereas iOS runs applications natively so those applications would need to be optimized for 64-bit.
Sent from my HTC Sensation using Tapatalk
android1234567 said:
Android wouldn't really need to be optimized for 64-bit like the iPhone 5s because Android uses a virtual machine (Dalvik) to run apps, whereas iOS runs applications natively so those applications would need to be optimized for 64-bit.
Sent from my HTC Sensation using Tapatalk
Click to expand...
Click to collapse
Thanks. learned something.
Toxina said:
so i saw that the apple a7 chip is actually just a snapdragon 800 processor just like our nexus 5, does that mean the nexus 5 kernel does support 64bit?
Click to expand...
Click to collapse
just FYI , right now 64bit on iOS is a gimmick , notice i said " right now" ... dont you find it odd Apple never mention specs ? didnt tell us what the CPU speed was , how much ram... but all of a sudden , they tell us its 64bit architecture? hmm
android1234567 said:
Android wouldn't really need to be optimized for 64-bit like the iPhone 5s because Android uses a virtual machine (Dalvik) to run apps, whereas iOS runs applications natively so those applications would need to be optimized for 64-bit.
Sent from my HTC Sensation using Tapatalk
Click to expand...
Click to collapse
Incorrect. Much,much, MUCH, of android is native code (even the dalvik interpreter), which is dominated by ARMv7 architecture at the moment. With the transition to 64 bit ARM (AArch64 mode on the ARMv8 processor), the kernel, drivers, bionic libc library, libgralloc (graphics), and countless other libraries need to be ported to 64 bit. This involves 64 bit compilers becoming release quality, and code reviews to ensure that pointer casts are handled appropriately for the transition to a larger address map.
However, there is nothing inherently better about '64 bit' and the Snapdragon 800 chip is a monster.
adma84 said:
Incorrect. Much,much, MUCH, of android is native code, which is currently ARMv7. With the transition to 64 bit ARM (AArch64 mode on the ARMv8 processor), the kernel, drivers, bionic libc library, libgralloc (graphics), and countless other libraries need to be ported to 64 bit. This involves 64 bit compilers becoming release quality, and code reviews to ensure that pointer casts are handled appropriately for the transition to a larger address map.
However, there is nothing inherently better about '64 bit' and the Snapdragon 800 chip is a monster.
Click to expand...
Click to collapse
Learn something new every day But the apps themselves on Android wouldn't need to be re-written for 64-bit like they do on the iPhone 5S, right?
Back to Apple's A7 chip, I think Apple did this to get a head start on 64-bit development; I doubt the iPhone 5S has 3.5GB+ of RAM so 64-bit doesn't seem practical for the 5S.
android1234567 said:
Learn something new every day But the apps themselves on Android wouldn't need to be re-written for 64-bit like they do on the iPhone 5S, right?
Back to Apple's A7 chip, I think Apple did this to get a head start on 64-bit development; I doubt the iPhone 5S has 3.5GB+ of RAM so 64-bit doesn't seem practical for the 5S.
Click to expand...
Click to collapse
Yes and No. Some Apps (most Games) run native code the would have to be rewitten in 64bit.
I think it has been confirmed that the 5S has 1GB of Ram.
64-bit is meh.. its going to take time for it to mature. Its still in its infant stages and will take time... but eventually down the road, it'll become the standard. For now, I don't think its that much of a thing to look at when buying a phone.
zephiK said:
64-bit is meh.. its going to take time for it to mature. Its still in its infant stages and will take time... but eventually down the road, it'll become the standard. For now, I don't think its that much of a thing to look at when buying a phone.
Click to expand...
Click to collapse
Yep. In fact, the best thing about 64 bit is the ability to see a 4GB+ memory space. ARMv8 does a nice job of cleaning up the instruction set (I spend my days writing ARMv8 right now), but I expect power to be an issue even at the cost of possible speed improvements due to doubling neon/VFP registers and other such improvements
adma84 said:
Yep. In fact, the best thing about 64 bit is the ability to see a 4GB+ memory space. ARMv8 does a nice job of cleaning up the instruction set (I spend my days writing ARMv8 right now), but I expect power to be an issue even at the cost of possible speed improvements due to doubling neon/VFP registers and other such improvements
Click to expand...
Click to collapse
This...
If the addressable mem space (RAM) goes unutilized, the cleaner instruction set remains the only pro. For now, gimmick.... Down the line, standard.
booooom
A7 is not by any means close to a Snapdragon, completely different designs. But similar performance though.
Sent from my GT-I9100 using Tapatalk 4