I would dig through the commits from William and Lasse. They recently implemented the x64 port. It was more work than a 32-bit architecture, since it involved also making parts of v8 work with 64-bits.
I would try to follow the same path they did, which parts, tests, etc they started with, and how they brought the pieces together. It seems like a MIPS port will be most similar to ARM, so you'll probably want to understand how that code generator works. Good luck -- dean On Sat, Sep 12, 2009 at 2:06 AM, A.Rames <[email protected]> wrote: > > I am glad to say on this group that Sigma Designs wants to port v8 to > the MIPS architecture and plans to contribute the code when it is > finished. > I am a new Sigma intern and I will be working on this project > (supervised by Sebastian Manciulea). > > After some time running tests, reading documentation about dynamic > compilation techniques, and reading v8's code, I am now thinking about > how to port v8 to MIPS. > > After discussing it briefly, the rough idea would be: > - To manage to compile v8 for MIPS. (without having it work) > - I guess I will then need to implement the whole (or most of it) > instruction set and test if I can correctly generate instructions > before really porting anything else. > - To port gradually each element, beginning by the most independent > elements. (cpu.h functions, higher level description of instructions, > etc) > - Continue to a higher level, beginning with the regexp part as both > interpreter and native mode are present. > > So this is my rough guess of how I should begin. However v8 > developers' (and other's as well) opinion and advice would be a great > help! > Are there any problems with my approach? Where would you begin? Do you > have any particular warning or advice? > > > Thanks! > > Alexandre > > > --~--~---------~--~----~------------~-------~--~----~ v8-users mailing list [email protected] http://groups.google.com/group/v8-users -~----------~----~----~----~------~----~------~--~---
