[v8-users] adding v8 pgm as a browser plugin

2015-02-26 Thread jency
Is it possible to add a v8 program as a plugin for a browser ?? -- -- v8-users mailing list v8-users@googlegroups.com http://groups.google.com/group/v8-users --- You received this message because you are subscribed to the Google Groups "v8-users" group. To unsubscribe from this group and stop

Re: [v8-users] Best environment to build V8

2015-02-26 Thread Louis Santillan
I build on Ubuntu ia32 & x86_64, as well as OSX 10.10 (which is now strictly x86_64). I also build on Debian arm (Raspberry Pi Model B, very slow). On Thu, Feb 26, 2015 at 5:38 PM, Jean-Philippe Déry < jeanphilippe.d...@gmail.com> wrote: > Hi! > > I'm currently trying to build V8 as a static lib

Re: [v8-users] Huge libv8_base.a (over 250Mb) when building for x64.release

2015-02-26 Thread Louis Santillan
I see you are linking in an awful lot of code. /home/schooten/bin/packages/android-ndk-r9d/toolchains/arm-linux-androideabi-4.6/prebuilt/linux-x86_64/bin/arm-linux-androideabi-g++ -Wl,-soname,libnative-activity.so -shared --sysroot=/home/schooten/bin/packages/android-ndk-r9d/platforms/android-9/ar

[v8-users] Best environment to build V8

2015-02-26 Thread Jean-Philippe Déry
Hi! I'm currently trying to build V8 as a static library for various platform and I'm having mixed results. I'm able to build for android but when I build for X64 release, the library gets over 250 MB. From what I'm understanding, the platform might have an impact so I'm thinking about using a

Re: [v8-users] ‘v8::Value’ to ‘v8::String conversion error

2015-02-26 Thread Louis Santillan
See [0] & [1] [0] https://github.com/v8/v8-git-mirror/blob/master/samples/shell.cc#L189 [1] https://github.com/v8/v8-git-mirror/blob/master/samples/shell.cc#L235 On Tue, Feb 24, 2015 at 10:05 PM, jency wrote: > I am trying to read a javascript function written in a file and retrieve it > using

Re: [v8-users] Add recognition of unused Arm opcode to prevent runtime error

2015-02-26 Thread Rodolph Perfetta
So m5_enableDebugFlag is a function which contains your special instruction followed by a mov pc, lr (standard return). I can see two issues: * your special instruction change lr where the return address is stored so your function will not return where it should. This is likely the cause for your

Re: [v8-users] Add recognition of unused Arm opcode to prevent runtime error

2015-02-26 Thread Malek Musleh
The purpose of My m5_enableDebugFlag () is to enable tracing (dissaembly, cache behavior, etc) within the simulator. A separate macro within the simulator is invoked for each one of these magic instructions: SIMPLE_OP(m5_enableDebugFlag, enable_debugflag_func, 0) #define enable_debugflag_func 0

Re: [v8-users] Add recognition of unused Arm opcode to prevent runtime error

2015-02-26 Thread Rodolph Perfetta
What does m5_enableDebugFlag(); do? Just emit a 32-bit instruction? Where to? For the builtin simulator, on an intel machine simply build the arm target: make arm.release. When the build system detect the mismatch between the host tool ISA and the target ISA it automatically build the simulator.

Re: [v8-users] Add recognition of unused Arm opcode to prevent runtime error

2015-02-26 Thread Malek Musleh
Hi Rudolph, Yes, I have been able to run a clean version of v8 on this other ARM simulator (gem5). I added support to the gem5 simulator to handle this unused opcode. I think it might be your second suggestion. In one of my instrumentations, I inserted the function after a __Push(), where in othe

Re: [v8-users] Add recognition of unused Arm opcode to prevent runtime error

2015-02-26 Thread Rodolph Perfetta
If I understood correctly you are using a modified arm simulator (not the V8 built-in one) to run V8, and this simulator returns "illegal instruction". V8 does not trap illegal instructions so the options I can think of: * your ARM simulator does not support ARMv7 with VFP, which is a requirement

[v8-users] Add recognition of unused Arm opcode to prevent runtime error

2015-02-26 Thread Malek Musleh
Hi, I've instrumented parts of the v8 source code to call a function from an external library, and have been able to get it compiled successfully, but am running into issues at runtime. Specifically, I am running v8 inside an arm simulator, and the instrumentation calls I added are recognized b