jegHegy
Now on LSD!
ok, i'll try to make this as short as i can. there are two things, the first idea is mine, and the second idea is a developer's at efnet #gp32dev (who's name i'm not sure i can reveal). these two things combined with a heavy ASM core written from scratch could be usable.
my idea: basically, we'll have to read the whole ROM by chopping it to chunks, disassemble it, and analyze the code, searching for the most frequently used addresses. then we precache the data from those offsets into RAM, and load other stuff realtime (if it takes a lot of time, even using a loading screen).
the other idea: parsing the disassembled ROM searching for code that can be executed natively on the gp32, and writing an executable file with the native code, and a few external calls to the emulator for other stuff.
writing the ASM core would take a lot of time though. maybe we could try with a C core first, and see how speed is. comments are welcome.
my idea: basically, we'll have to read the whole ROM by chopping it to chunks, disassemble it, and analyze the code, searching for the most frequently used addresses. then we precache the data from those offsets into RAM, and load other stuff realtime (if it takes a lot of time, even using a loading screen).
the other idea: parsing the disassembled ROM searching for code that can be executed natively on the gp32, and writing an executable file with the native code, and a few external calls to the emulator for other stuff.
writing the ASM core would take a lot of time though. maybe we could try with a C core first, and see how speed is. comments are welcome.