8 ms·
You aren't necessarily saying differently, but it's worth noting that Android has supported x86 for quite some time (the platform, the runtime, the NDK cross-co
by personZ 12y ago
You aren't necessarily saying differently, but it's worth noting that Android has supported x86 for quite some time (the platform, the runtime, the NDK cross-compiling, and the x86 emulator image -- all have been available for a couple of years).
And to the other comment (from a different user, though I am responding here while on the topic of x86) claiming that Intel support doesn't matter -- it very much matters. Already there are a large number of deployed x86 devices (even ones that people don't realize are x86, like the Dell Venue 7), and Broadwell will only accelerate that. Supporting multiple platforms is awesome.
- suyash 12y agoIt has supported for a long time but that's for C++ native development not for Java developers. This is a big change in x86 support in L. Which other comment, I never said it doesn't matter.
- lnanek2 12y agoEh, Java only Android apps have run fine on x86 Android devices for years. There's a consumer x86 tablet out there I've run stuff on - won one of the tablets at a hackathon in NYC last year for getting a WebRTC client running on it. Heck, even native ARM lib stuff is supposed to run fine, but slow, due to some some special libhoudini translation layer Intel made to handle it.
- kllrnohj 12y agoUh, no it isn't? Dalvik has had x86 codegen since ICS: https://android.googlesource.com/platform/dalvik/+/ics-mr0/vm/compiler/codegen/ https://android.googlesource.com/platform/dalvik/+/ics-mr0/v... And that's for JIT codegen, the interpreter will obviously run just fine on every architecture. MIPS becamse first-class supported in KitKat, by the way.