Hi Wan Li - I was not referring to build differences between Android and non-Android (though there are some) but rather to maintaining release branches for older versions of v8.
Google maintains release branches for older versions that are still in active use, and we do a similar thing in our github repo. For instance Android Honeycomb mr2 uses v8 version 2.5.9.20. Gingerbread and Froyo use older versions of v8. For the Mips versions of Android we have moved to a v8 based on version 3.2.3. And for Mips, we have another issue in that the v8-team removed the classic code-generator as of version 3.2.7. Since we have not yet finished development of the Crankshaft code-generator, that limits our performance on more recent builds. This will become a non-issue as soon as we get our Crankshaft version released. So depending on what you want to achieve, you may not want to pull our latest version (or the latest from the v8-team's tree), but rather use an older release branch. If you are using Android, I recommend that you just get the included v8 as part of our normal mips-android release. thanks, paul On Jun 28, 2011, at 7:29 PM, Wan Li wrote: > Hi Paul, > > Thanks for your clarify. > I don't quite understand the differences between Android and non-Android > versions. Is that related to the implementation of V8 itself or build config? > > On Wed, Jun 29, 2011 at 6:04 AM, Paul Lind <[email protected]> wrote: > Hi Felix - > > I work on the mips port, and can answer some of your questions: > > 1. We currently pass all the tests. > > 2. I can't speak for the v8-team. This post from Mikail Naganov may clarify > the current situation: > http://groups.google.com/group/v8-users/msg/f9946f247ac27541 > > 3. We are in-progress with Crankshaft, have it partially working, and running > some of the v8-benchmark tests successfully. I am guessing that we are a > couple months from having something in releasable form, and further > optimizations will continue well after that. We will likely start submitting > our Crankshaft code upstream to the v8-team before that timeframe. > > All our work is done open source on github here: > https://github.com/paul99/v8m-rb > > We also maintain versions of v8 for the mips-android builds. Those will > continue to use the "classic" code generator for v8 (for higher performance), > until we have our Crankshaft code ready to release. If you have need for a > non-android version of v8 for mips, we can talk about which version/branch > would be most appropriate for you. > > 4. We have not planned to do this, but it is an interesting idea. As we get > further along with Crankshaft work, we may do such a thing. > > Hope this helps, > > paul > > On Jun 28, 2011, at 12:52 AM, Felix Wan wrote: > >> Hi gurus, >> >> There are a lot MIPS port work taking place. I'd like to known if there is a >> roadmap about when shall we see these happen? >> 1. Pass all the test cases? >> 2. MIPS goes officially supported as ARM did? >> 3. Crankshaft support >> 4. Benchmark chart as arewefastyet? >> >> -- >> v8-users mailing list >> [email protected] >> http://groups.google.com/group/v8-users > > > -- > v8-users mailing list > [email protected] > http://groups.google.com/group/v8-users > > > > -- > >: ~ > > -- > v8-users mailing list > [email protected] > http://groups.google.com/group/v8-users -- v8-users mailing list [email protected] http://groups.google.com/group/v8-users
