Thanks. So you mean to say that when i compile a native code using the prebuilt toolchain of Android for emulator, the ARM instructions generated is in no way limited by some limitations of the emulator(if any).
ajay On Feb 26, 12:55 am, David Turner <di...@android.com> wrote: > As far ar I know, the system images that are provided with the SDK are built > in the same way than the ones that run on retail Dream/G1 and Magic/MyTouch > devices. > In other words, they are not tuned specifically for the emulator (but they > contain emulator-specific code that is not part of the system image of > production devices). > > Also, the kernel images must be different between the emulator and a real > device, but you probably already knew that :-) > > On Tue, Feb 23, 2010 at 7:55 AM, Ajay <meajaypil...@gmail.com> wrote: > > Hi, > > I am running an Android image built for the emulator on an actual > > ARMv6 platform. Although it does work perfectly well, i am curious if > > i am taking a performance hit due to that. > > I wonder if the android emulator has a incomplete support for the ARM > > instruction set and the prebuilt toolchain is tuned for that > > constraint of the emulator. > > > thank you > > ajay > > > -- > > unsubscribe: > > android-porting+unsubscr...@googlegroups.com<android-porting%2bunsubscr...@googlegroups.com> > > website:http://groups.google.com/group/android-porting -- unsubscribe: android-porting+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-porting
