Re: [v8-users] List of V8 GYPFLAGS

of the Yun except for a reduced form factor (the hardware is the same : Atheros AR9331 as linux cpu and Atmel ATmega32u4 as MCU) Thank you in advance for everything you can find about this issue Regards, Arturo Il giorno mercoledì 11 febbraio 2015 06:24:37 UTC+1, paul lind ha

Re: [v8-users] List of V8 GYPFLAGS

to force the build with the default FPU options enabled and report here in the list. I hope to get my Atheros9300 CPU based board working with this build... Regards, Arturo Il giorno mercoledì 11 febbraio 2015 00:06:10 UTC+1, paul lind ha scritto: Sorry, but that is not going to work. From

Re: [v8-users] List of V8 GYPFLAGS

Sorry, but that is not going to work. From your earlier screenshot I am guessing that you previously used node 10, with v8 3.14 from our old github repo. The good news is that the MIPS big-endian support is all upstream in v8 repo since 3.26, which of course includes the 3.28 version in node

Re: [v8-users] MIPS V8 performance regression from Chromium M31 to M37?

it may be moot. Managed to get it build correctly for our platform but running into SIGILL when running Octane, so either something is horribly corrupted or I failed to describe our platform correctly to the build process :). On Monday, 3 November 2014 19:59:16 UTC-5, paul lind wrote: Hi

Re: [v8-users] MIPS V8 performance regression from Chromium M31 to M37?

Very sorry Stephen, that is crazy bad. We'll get on this immediately and get it understood and fixed asap. paul On Nov 3, 2014, at 2:59 PM, Stephen smcgr...@google.com wrote: Dear v8-users, We have a port of Chromium to a MIPS(el) embedded system, and are currently in the process of

Re: [v8-users] mips support for n32 abi

Hi Jacob - Currently, we do not plan to support n32 ABI in v8, but I'm happy to give you some pointers that should help if you want to give it a go. You're right that it is mostly about FP register use and the ABI's when calling between C code and the JIT'ed code. There is good info in

Re: [v8-users] Re: [v8 material ]

Sam - Another good source of knowledge about v8 internals are some blog posts that Andy Wingo wrote over the past 2 or 3 years. Here are some related to v8 and to some of the other javascript implementations: http://wingolog.org/tags/v8 Be sure to read the comments on the posts as well...

Re: [v8-users] Using v8 within android for armeabi-v7a and mips

Hi Kevin - Regarding your MIPS question, you are best off pulling from Google's release branches, which match up to major Chrome releases. Those will have received the most testing, on all platforms. The latest right now is 3.12, and Android Jelly Bean is using 3.9, if that matters to you at

Re: [v8-users] Re: GC crash

Hi Evgeny - I'm one of the maintainers of the mips port, and as Yang mentioned, we're the ones who can help you with bugs there. My testing shows that our test boards are working fine at the rev you pulled, including the regress-84234.js test you mentioned below. I suggest that you do file

Re: [v8-users] Re: Low benchmark score on MIPS platform

Another mips board, 1.3 GHz, 256k L2 (ver 3.11.8, r11683) Richards: 1284 DeltaBlue: 1349 Crypto: 1383 RayTrace: 1230 EarleyBoyer: 2492 RegExp: 323 Splay: 456 NavierStokes: 664 Score (version 7): 959 On May 30, 2012, at 9:12 AM, Paul Lind wrote

Re: [v8-users] Re: Low benchmark score on MIPS platform

Lawrence - An 800MHz mips board we test with gets this result: Richards: 419 DeltaBlue: 733 Crypto: 996 RayTrace: 531 EarleyBoyer: 1531 RegExp: 214 Splay: 413 NavierStokes: 419 Score (version 7): 556 A 900 MHz board with 512k L2 get this: Richards: 966 DeltaBlue: 1295 Crypto: 1222

Re: [v8-users] help to debug v8 slow down

Hi Levent - v8 at r10875 doesn't even build for me, so I cannot explain your 'slowdown'. That rev on trunk is version 3.9.13. If you move to 3.9.14 (r10894), which was pushed just 24 hours later, the mips port will build and run fine, and I verified that the performance is normal (running v8

Re: [v8-users] Dumb question!

Hi Keith -- Prefix the option with 'no' to force it false. In your example: '--nouse_idle_notification' paul On Aug 19, 2011, at 11:34 AM, Keith Johnston wrote: I see several flags of type boolean. If the default value is true, how do I set these options to false? Does setting the flag

Re: [v8-users] MIPS port roadmap

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 pau...@cruzio.com wrote: Hi Felix - I work on the mips port, and can answer

Re: [v8-users] MIPS port roadmap

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

Re: [v8-users] js2c.py endianness issue mips

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

Re: [v8-users] v8 mips cross compile

Hi Jeff - The v8 MIPS port is a work in progress. The code in the google tree is old and not functional. We are developing the code in an independent repository on github: https://github.com/paul99/v8m-rb Use the master branch. This code is behind the current google tree, and we are working

Re: [v8-users] Print out JIT debugging information

Hi Yehuda - The v8 shell has a lot of options for seeing the generated code. Build the shell in debug mode: scons mode=debug sample=shell -jNN Then run your code with these options, as a start: shell_g --debug-code --print-code xxx.js Other useful opts are: --print-code-stubs --trace-codegen

Re: [v8-users] Print out JIT debugging information

I should add that these flags were mostly intended for development of v8 itself, and it is not necessarily easy to correlate the generated code with your javascript source. The --print-ast option can help with this. Paul On Dec 8, 2010, at 9:43 PM, Paul Lind pau...@cruzio.com wrote: Hi

Re: [v8-users] help w/ install

Hi Hank - It appears that scons is defaulting to build IA32 arch, and is compiling using flag '-m32'. But you likely do not have the 32-bit compatibility libraries installed, so the link step fails. The easiest thing to do is tell scons to build x64 architecture: scons arch=x64

Re: [v8-users] Segmentation fault when creating new v8 context.

Hi Nilima - Was this on v8mips, or on v8 for one of the other architectures? If for v8mips, are you running big-endian or little-endian? thanks, paul On Aug 10, 2010, at 3:11 AM, Nilima Chavan wrote: Hi All, I am getting segmentation fault while using v8 library when creating new v8

[v8-users] Re: MIPS status?

Hi Tony - The mips porting activity is moving forward, and we are making good progress. The mips code in the google v8 repository is quite old, and is not functional. We are maintaining the project separately here (http://github.com/ paul99/v8mips) until things are complete enough to restart the

Re: [v8-users] Re: Building v8 for MIPs platform.

. But giving endianness errors for shell. So I have question here, I am going to use libv8.a with v8cgi and apache. So can I survive currently with just v8 library build. I do not require shell at this point of time. Thanks Regards, Nilima On Tue, Jul 13, 2010 at 11:32 PM, paul lind

[v8-users] Re: Building v8 for MIPs platform.

Hi Nilima - I'll try to answer your questions: 1. Alexandre is correct, you must make sure you are using the 'integration' branch (it is the default). 2. Per your command, you built libv8 for arch=mips, but you are trying to build your shell for the simulator (simulator=mips). You cannot mix