4. jan. 2011 04.50 skrev Paul Lind <[email protected]>: > Hi Jeff - > v8 for mips has never been built/tested for big-endian. We'd like to do this > at some point, but it has been lower priority than getting the baseline > little-endian port finished, and submitted back to Google. And now there is > the new work for Crankshaft, which also will take priority. > During the port we have noted some areas that we are certain will need > attention. You likely just spotted another one in js2c.py. > But I believe that the bigger issue is that v8 as a whole has never been run > on any big-endian architecture to my knowledge. While Arm processors are > capable of running big-endian, it does not appear that there is support for > that in v8. (if anyone knows otherwise, please do correct me on this)
No, this correct, V8 has never been run on a big endian architecture. There are some ARM machines where the floating point numbers are mixed endian (little endian byte order, big endian word order) and some support can be seen in the source for that. > I suspect there will be many issues to find and debug. If you are willing to > take some of this on, I could point you at specific issues I'm aware of, but > I would not expect this to be easy. > thanks, > paul > On Jan 3, 2011, at 6:29 PM, Jeff wrote: > > We were able to get node.js + v8 working on mips little endian but not on > mips big endian - we suspect it's an issue with the js2c.py script that > converts the javascript code to a c character array. Is this a known > issue, and is there a fix? > > Thanks, > Jeff > > -- > 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 -- Erik Corry, Software Engineer Google Denmark ApS - Frederiksborggade 20B, 1 sal, 1360 København K - Denmark - CVR nr. 28 86 69 84 -- v8-users mailing list [email protected] http://groups.google.com/group/v8-users
