On Jul 24, 6:50 pm, zhtlancer <[email protected]> wrote: > I've already read the doc, but I didn't find any guide about building the > portable interpreter seperately. I looked into the mterp/out dir, and > thought that the InterpC-portstd.c, InterpC-allstubs.c, InterpAsm-allstubs.S > should be the portable source. But it seems that they don't work...
I'm not quite sure what you're after. If you look in dalvik/vm/Android.mk, you'll see a bunch of platform- specific "ifeq" lines. If nothing matches, it includes a couple of things from arch/generic and the "allstubs" interpreter. The latter is portable, but slow. As the porting doc says, at any given time you have three interpreters: "fast", "portable", and "debug". You choose between the first two with "-Xint:fast" and "-Xint:portable", and the latter kicks in when you attach a debugger or start profiling. The "portstd" files are the sources for the "portable" interpreter. What do you mean by "they don't work"? --~--~---------~--~----~------------~-------~--~----~ unsubscribe: [email protected] website: http://groups.google.com/group/android-porting -~----------~----~----~----~------~----~------~--~---
