Re: [v8-users] Re: xcode project and arm target

Hi Rolando, to answer a few points from your previous email: > the ARM target of the xcode project is not compiling ARM code It is compiling the arm JIT for x86 architecture: V8 includes a small simulator which allows it to run, albeit slowly, the arm JIT on non arm platforms. > I disabled thu

Re: [v8-users] Cross-compiling V8 for ARMv4T

V8 does not support armv4t, but it does support armv4 so try -march=armv4 On 1 September 2010 19:17, Emre wrote: > Hi all: > > I am trying to cross-compile V8 for friendlyArm (mini2440) board > (Samsung S3C2440). I get the following error: > > /home/me/Dev/mini2440/oe/build/cross/armv4t/bin/arm-

Re: [v8-users] Date and Math.random issues on armV4 (arm920t)

Hi, I couldn't reproduce your issue, an armv4 build of bleeding_edge gives me the right result. Are the C libraries on your platform working properly? Could you try and narrow it down a bit: is it Math.floor or Math.random (or both) which is an issue? Cheers, Rodolph. On 25 November 2010 14:09,

Re: [v8-users] armv7-a : For thumb inter-working we require an architecture which supports blx

The minimun requirements are: armv4 without interworking or armv5t with interworking. The build system will default to whatever your compiler defaults are, which here seem to be armv4t with interworking hence the error. as Erik explained you can manually add some compiler options such as "-march=

Re: [v8-users] Re: Date and Math.random issues on armV4 (arm920t)

Hi Julien, Is there something preventing you moving to a newer software platform? OABI has been deprecated for quite some time and its support is likely to be removed in a number projects and you are likely to hit more and more these kind of issues. how about debian? Cheers, Rodolph. On 25 Decem

Re: [v8-users] Cross compile for arm926ej-s gives 'no blx' error.

This seems more like a toolchain issue than a build script issue. Get rid of "-mcpu=arm926ej-s" and it should work. If you want to target 926 then use "-mtune=arm926ej-s". In general I prefer using march/mtune to mcpu, and the wiki page you mention only uses mtune not mcpu. Cheers, Rodolph. On 21

Re: [v8-users] Re: Date and Math.random issues on armV4 (arm920t)

Hi Yoann, The issue look to be around the ABI on your platform: is it really OABI or some kind of variant. Anyway, as I mentioned before, OABI has been deprecated for quite a while, so moving to a more recent filesystem is your best chance. Cheers, Rodolph. On 14 February 2011 14:04, Yoann Sculo

Re: [v8-users] ARM support - which architecture variants?

V8 can run on ARMv4 devices (non T though). There is no interpreter in V8 so you will be using the JIT every time, perfromance should be good (keep in mind CPU like 926-ej-s do not have L2 cache and this is going to have a visible impact). There is a new JIT infrastructure being developed (cranksh

Re: [v8-users] Re: ARM support - which architecture variants?

e frame for when nocrankshaft will be > > > > > > > deprecated? > > > > > > > > > > Thanks, > > > > > > > Hugo > > > > > > > > > > On Feb 23, 9:14 pm, S�ren Gjesse > wrote: > > > >

Re: [v8-users] Re: ARM support - which architecture variants?

flags="--crankshaft" and --js-flags="--nocrankshaft" > > > options. > > > But the V8 scores are nearly same. > > > > > V8::DisableCrankshaft() function is called from cpu-arm.cc. > > > I think Chromium is not able to parse

Re: [v8-users] v8 compatible CPUs : HTC Dream

v8 will work on an ARMv6 cpu though Crankshaft (the optimising compiler) will not be used. Cheers, Rodolph. On 7 July 2011 16:25, Jose Manuel Cantera Fonseca < jmcanterafons...@gmail.com> wrote: > Hi there, > > I'm trying to run v8 together with Webkit in a custom Android build for HTC > Dream.

Re: [v8-users] Any way to compile V8 for PPC?

Code generation is mandatory. Rodolph. On 9 July 2011 10:34, Egor Egorov wrote: > > Is there any way I could compile V8 for a ppc32 machine (running linux)? Or > code generation is mandatory in V8? > > > > -- > v8-users mailing list > v8-users@googlegroups.com > http://groups.google.com/group/

Re: [v8-users] v8 compatible CPUs : HTC Dream

s 1. >> >> Are you defining CAN_USE_UNALIGNED_ACCESSES to 1 when compiling? >> >> Do you have any idea whether the runtime issue you have is due to JIT code >> generated by V8? >> >> Regards, >> Søren >> >> On Fri, Jul 8, 2011 at 08:47, Jose Manu

Re: [v8-users] v8 compatible CPUs : HTC Dream

imulator:none': { >> 'CCFLAGS': ['-mfloat-abi=softfp'], >> } >> }, >> 'armeabi:hard' : { >> 'CPPDEFINES' : ['USE_EABI_HARDFLOAT=1', >> 'CAN_USE_VFP_INSTRUCTIONS'

Re: [v8-users] Cross compile for RaspberryPi (arm64)

Hi Kin, Unlike Intel the arm64 and arm32 toolchains are two different toolchains. The one you are using is for 32-bit arm only hence only arm32 is defined. The 64-bit version will be named something like gcc-linaro-aarch64-… You are probably aware of it but only the Raspberry Pi 3 can run arm64 c

Re: [v8-users] Cross compile for RaspberryPi (arm64)

://github.com/raspberrypi/tools/tree/master/arm-bcm2708) Where can I find a gcc-linaro-aarch64-* ? Thanks, Kin On Mon, Jun 20, 2016 at 11:26 AM, Rodolph Perfetta < rodolph.perfe...@gmail.com> wrote: > Hi Kin, > > Unlike Intel the arm64 and arm32 toolchains are two different toolchains. &g

Re: [v8-users] Re: Building V8 engine for Windows CE6-ARM target

V8 doesn't support WinCE, never has, so it is unlikely you'll find documentation on the subject. WinCE is rather old, so before trying anything to get V8 building on this target, you may want to ensure your CPU meets the minimum requirements: ARMv6 and VFPv2. Rodolph On Tue, 27 Sep 2016 at 14:57

Re: [v8-users] Cross Compiling for Raspberry

The build system will generate a host binary to generate snapshots. IIRC disabling snapshot (snapshot=off) will still result in the host binary being built. So why not installing the host tools completely? V8 3.30 is rather old and unsupported though I presume this is a rethinkDB requirement. Ther

Re: [v8-users] Build v8 for arm on linux

Hi, have you tried building using GYP and using ./tools/cross_build_gcc.sh? I can't really help with the issue on the Mac but just one observation: if you use arm-linux-gnueabihf-gcc then the float_abi will default to hardfp. Rodolph On Mon, 24 Oct 2016 at 15:17 ibon tolosana wrote: > Hi there

Re: [v8-users] Build v8 for arm on linux

f the hf version ? I > though the abi would be softfp instead of hard though. > > Can you point me somewhere where I could have a proper example for > cross_compile_gcc ? > > Thanks. > > > > > El martes, 25 de octubre de 2016, 17:16:18 (UTC+2), Rodolph Perfetta > esc

Re: [v8-users] V8 for Android undefined symbol v8::base::SysInfo::NumberOfProcessors()

Hi, I am not sure I follow what you are doing: if your cross compilation was successful why do you need to build and link mksnapshot again? Secondly cross compiling for raspberry will target arm linux, but the lines you posted reference android_arm. Did you intend to mix both target? Rodolph On

Re: [v8-users] V8 for Android undefined symbol v8::base::SysInfo::NumberOfProcessors()

a different compilation. Nothing to do > with this. > > Now i try to compile v8 for android. > And i get that missing symbol. > > Sorry for the misunderstanding. > > thanks. > > > El viernes, 28 de octubre de 2016, 20:48:19 (UTC+2), Rodolph Perfetta > escribió:

Re: [v8-users] Cross-compile for arm64 (iOS)

You can't disable the JIT, it is required for V8 to run. On Sun, 5 Mar 2017 at 08:46 Lukas Kollmer wrote: > Thanks! > > Is iOS not supported because v8 would not compile for iOS or because it > wouldn't be allowed by Apple? > I've seen some screenshots of v8 running on iOS 4 or 5 so running on i

Re: [v8-users] Issues Building v8 from Source

The script is failing to run a command, have you tried running the command on its own? Maybe you don't have pkg-config installed. Rodolph On Tue, 19 Sep 2017 at 07:48 Benny Mei wrote: > Hi all, > > I am attempting to build v8 from source by following the directions here >

Re: [v8-users] Running V8 on ARM64 Windows?

Hi, The arm64 port follows the procedure call standard defined here: http://infocenter.arm.com/help/topic/com.arm.doc.ihi0055b/IHI0055B_aapcs64.pdf , I do not know if/how Windows on Arm differs. The main interface points are JSEntryStub, CEntryStub,and DirectCEntryStub (src/arm64/code-stub-arm64.c

Re: [v8-users] LP64 dependence of arm64 backend?

As far as I recall this was a preventive check as we didn't have arm64 LLP64 system to test on. I don't believe there is anything incompatible with LLP64. On Wed, 18 Apr 2018 at 16:06 Ben Noordhuis wrote: > On Wed, Apr 18, 2018 at 8:20 PM, Thomson Tan wrote: > > The current ARM64 backend requir

Re: [v8-users] Re: using custom toolchain for V8 builds

A long shot but a while ago to build on Raspberry I would have the following flags: GYPFLAGS="-Dlinux_use_bundled_gold=0 -Dtarget_arch=arm -Dclang=0" and the following build command: tools/cross_build_gcc.sh /bin/arm-linux-gnueabihf- arm.release armfpu=vfp armfloatabi=hard arm_version=6. No guaran

Re: [v8-users] Building V8

To use the bundled tools, you need a 64-bit machine. if this is not an option you could try installing all the dependencies yourself (and disabling the use of bundled tools by specifying is_clang=false and probably more), but I don't believe this is documented. On Mon, 25 Mar 2019 at 17:36, wrot

Re: [v8-users] Building V8

. On Tue, 26 Mar 2019 at 09:00, Marto Parts wrote: > So long story short I can’t run v8 cause of 32 bit ? > > On Tue, 26 Mar 2019 at 00:27, Rodolph Perfetta > wrote: > >> To use the bundled tools, you need a 64-bit machine. >> >> if this is not an option

Re: [v8-users] Building V8

oesn’t work > otherwise I will be happy to run it in the 64bit machine > > On Tue, 26 Mar 2019 at 15:19, Rodolph Perfetta > wrote: > >> You can build a 32-bit v8 binary on a 64-bit machine and the resulting >> binary will run on a 32-bit machine. >> >> If you

Re: [v8-users] how to run v8 in debug mode so I can use the %DebugPrint

To be able to use native functions starting with % such as %DebugPrint you need to pass --allow-natives-syntax to d8 on the command line. Cheers, Rodolph On Thu, 15 Aug 2019 at 09:26, 杨亮 wrote: > hi，I want to know how I can run d8 in debug mode so I can > use %DebugPrint command，I can just

Re: [v8-users] how to run v8 in debug mode so I can use the %DebugPrint

n d8 In the > debug mode, but I don't know how. > > On Thursday, August 15, 2019 at 10:38:07 PM UTC+8, Rodolph Perfetta wrote: >> >> To be able to use native functions starting with % such as %DebugPrint >> you need to pass --allow-natives-syntax to d8 on the command line

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

Hi Kevin, The standalone V8 for ARM builds for armv7+vfpv3 by default using gyp. V8 has two compilers, one non optimising which compiles everything the first time and an optimising compiler (crankshaft) for hotspots. To use crankshaft on ARM you need armv7+vfpv3. The non optimising compiler works

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

Would I have to > change the Makefile to create an armv5 build? > > Cheers, > Kevin > > On 03.09.2012, at 13:16, Rodolph Perfetta wrote: > >> Hi Kevin, >> >> The standalone V8 for ARM builds for armv7+vfpv3 by default using gyp. >> >> V8 has

Re: [v8-users] V8 build on Linux using GYP

Add strictaliasing=off to your build command. Alternatively use a newer gcc. 4.1.2 is old and the code generated by it on ARM is not very good. On 9 January 2013 11:29, Neha wrote: > Hi, > > I tried building v8_master using gyp on linux. > make used is 3.81, gcc 4.1.2. python is Python-2.7.3.

Re: [v8-users] V8 build on Linux using GYP

e > code got compiled with this option. > What are the implications of using this option when i want to further use > V8 with my application? > > > > On Wednesday, January 9, 2013 5:22:28 PM UTC+5:30, Rodolph Perfetta wrote: > >> Add strictaliasing=off to your build co

Re: [v8-users] How to build V8 for Android armeabi, rather than armeabi-v7a ?

Could you give more info on the error you are seeing at load time? On 8 April 2013 19:49, Robin Watts wrote: > Hi all, > > *Some background:* > > I am one of the authors of MuPDF, a cross platform open source PDF viewer. > Recently we have been adding support for form filling etc, which requir

Re: [v8-users] How to build V8 for Android armeabi, rather than armeabi-v7a ?

It doesn't seem to be in V8 generated code so try forcing the build system to target armv5: export CC=gcc -march=armv5 export CXX=g++ -march=armv5 then your make command On 9 April 2013 00:43, Robin Watts wrote: > On Monday, 8 April 2013 21:14:04 UTC+1, Rodolph Perfetta wrote: > &

Re: [v8-users] How to build V8 for Android armeabi, rather than armeabi-v7a ?

Which CPU are you running the armeabi version on? V8 supports ARMv6 + VFPv2 so it doesn't have to be on v7. If you are looking at pre ARMv6 support then as you said you should disable V8 for this target (v3.9 should work but not future versions). The trace you sent looks like it maybe an arm/thumb

Re: [v8-users] How to build V8 for Android armeabi, rather than armeabi-v7a ?

I should probably have asked before, but what makes you think the crash comes from V8? Do you have a more precise trace? On 9 April 2013 20:40, Rodolph Perfetta wrote: > Which CPU are you running the armeabi version on? V8 supports ARMv6 + > VFPv2 so it doesn't have to be on v7.

Re: [v8-users] scons: *** No SConstruct file found.

Scons has been deprecated and removed, use gyp to build now: https://code.google.com/p/v8/wiki/BuildingWithGYP On 26 April 2013 07:59, Robert Main wrote: > I'm having a similar problem but my v8 directory doesn't seem to contain a > scons file. Is the scons file somewhere else now? > > On Wedne

Re: [v8-users] Run cctest crashed on armv6

Does the debug version of V8 reports the same error? On 20 May 2013 07:10, Zen Harry wrote: > I got a crash on android devices while running cctest. Here is what I do: > >1. compile the v8 code (v3.19.0, v3.18.5, v3.17.12) with command: make >android_arm.release -j9 armv7=false >2.

Re: [v8-users] Re: Cross compiling for V8 for Xilinx ARM doesn't work

Try as stated by the wiki, then if you still have some errors, provide some more info: toolchain version, platform, etc. On 3 July 2013 14:32, Benedikt Naessens wrote: > It is stated in https://code.google.com/p/v8/wiki/BuildingWithGYP , that: > > >> export LINK=/path/to/cross-compile-g++ >>>

Re: [v8-users] Floating point error

Hi Benedikt, The exact command which triggered the failure would be useful, usually it is just above the "# Fatal ..." comment. Have you tried make arm.debug armfloatabi=hard armv7=true armfpu=vfp (in other word is your platform hard fp?) On 4 July 2013 12:06, Ben Noordhuis wrote: > On Thu,

Re: [v8-users] Floating point error

bled automatically ? Or do I need to specify this > explicitly ? > > Shouldn't soft fp work anyway, regardless of the fact that hard fp is > possible ? > > Op donderdag 4 juli 2013 16:06:45 UTC+2 schreef Rodolph Perfetta het > volgende: > >> Hi Benedikt, >>

Re: [v8-users] Floating point error

When you say "I read that if you speciify armfpu option, you need to use s0ftfp instead of hard", you mean gcc option or V8 make options? Also you mentioned print(2.2*1.1) works, does this mean it prints the right result or just that it doesn't crash? Have you tried writing a small C program doing

Re: [v8-users] Floating point error

4.4, but just refers to the fact that the va_list has > changed from GCC 4.4 on (since we are using 4.7.2) > > > > Op vrijdag 5 juli 2013 15:34:12 UTC+2 schreef Rodolph Perfetta het > volgende: > >> When you say "I read that if you speciify armfpu option, you need to us

Re: [v8-users] Soft Floating Point support

The question is does v8 work when there is no hardware floating point present and the answer is no. softfp is the name of the abi which assumes hardware floating point but uses integer result for function call. Nowadays a lot of software on ARM (all the ubuntu packages for example) are compile fo

Re: [v8-users] Soft Floating Point support

2013 11:21, Ben Noordhuis wrote: > On Mon, Aug 5, 2013 at 12:07 PM, Rodolph Perfetta > wrote: > > The question is does v8 work when there is no hardware floating point > > present and the answer is no. > > > > softfp is the name of the abi which assumes hard

Re: [v8-users] Soft Floating Point support

running without VFP (in the Crankshaft section). > Is there any option to build V8 without vfp support? > Even if it is only for developers, we would like to try and see if it > meets with our performance requirements. > > Warm Regards, > JK > > > On Monday, August 5, 20

Re: [v8-users] Building v8 for ARMv5

V8 requires hardware floating point. Regards, Rodolph. On 28 August 2013 14:53, wrote: > I'm trying to use version 3.20.16 of v8 under an ARM926ej-s (ARMv5) board, > where /proc/cpuinfo shows the following information: > > # cat /proc/cpuinfo > Processor : ARM926EJ-S rev 5 (v5l) > BogoMIPS :

Re: [v8-users] Cross compiling V8 for ARM on Windows

Have read the wiki: https://code.google.com/p/v8/wiki/BuildingWithGYP Cheers, Rodolph. On 7 October 2013 12:30, Mihail Slavchev wrote: > Hello, > > I am trying to compile V8 for ARM using cygwin and ndk-r9. I get the > following error: > > CXX(host) > /home/slavchev/test/node/deps/v8/out/and

Re: [v8-users] Re: Discontinuation of V8 support for ARM chips without VFPv2

Hi Tom, Can you confirm this is a VFP issue: * adb shell cat /proc/cpuinfo on the device will tell you if you have VFP * what instruction is generating the fault? On a side note reverting the commit on a post 3.18 V8 will not work. Cheers, Rodolph. On 30 October 2013 11:35, Tom Jacobs wrot

Re: [v8-users] Re: Discontinuation of V8 support for ARM chips without VFPv2

1:31:54.78030-30/? I/DEBUG﹕ be984768 001d > 10-31 21:31:54.79130-30/? I/DEBUG﹕ be98476c b00103a4 > 10-31 21:31:54.79130-30/? I/DEBUG﹕ be984770 b00103a4 > 10-31 21:31:54.79130-30/? I/DEBUG﹕ be984774 2730 > 10-31 21:31:54.79130-30/? I/

Re: [v8-users] Re: v8 on Cortex-M3?

While you can run Javascript on any hardware, you won't be able to reuse common JavaScript VMs (wether be it V8, JavaScriptCore or Mozilla's engine) on a Cortex-M CPU. The main limitations are: * Thumb/Thumb2 only, though JavaScriptCore does generate Thumb2. * no mmu so no fully featured OS such

Re: [v8-users] Build error when cross compiling for ARM

it seems related to i18n, try make arm.debug i18nsupport=off On 18 December 2013 18:19, Hendrik Greving wrote: > Hi I am getting the following build error. I am setting CXX/LINK to an ARM > cross compiler (on x86). I am compiling with make arm.debug. > > /net/pc69.smi.local/local_disk/hgreving/v

Re: [v8-users] Building V8 for ARMv6 (Raspberry Pi), got illegal instruction (movw)

I sounds like auto detection is failing again, override it: --noenable-mls should do it. I can't push a patch right now so keep reporting any issues. Thanks, Rodolph. On 22 July 2014 15:08, Dirk Grabbert wrote: > Ok, I'm able to start the example shell right now. But I got the next > problem.

Re: [v8-users] Re: v8 on Cortex-M3?

v8 does thing like reserving memory and committing it when needed. On 28 July 2014 09:35, Dirk Grabbert wrote: > What's reason a mmu is needed by v8? I got a Cortex M3 with ucLinux. RAM > and Thumb2 are given. > > Am Donnerstag, 21. November 2013 19:33:57 UTC+1 schrieb

Re: [v8-users] Re: v8 on Cortex-M3?

y, but I don't see why a MMU is needed. > > Does V8 access the registers of the MMU directly or are there any syscalls > that does not or only limited work? > > Am Montag, 28. Juli 2014 11:06:52 UTC+2 schrieb Rodolph Perfetta: >> >> v8 does thing like reserving memory an

Re: [v8-users] Building V8 for ARM64 in MSVC2012

There is nothing fundamentally preventing an LLP64 system to build/run arm64 but it was never tested hence not supported. Some re-factoring is probably required (don't forget constants). As Sven said, patches welcome. On 8 August 2014 07:21, Sven Panne wrote: > On Thu, Aug 7, 2014 at 11:50 PM,

Re: [v8-users] Re: Cross compiling for raspberry pi

I may be missing something but in your example you are using x64 libs in your cross compilation, how could this work? Rodolph. On 9 January 2015 at 17:56, Milan Pandurov wrote: > That's pretty sad. I noticed that there are not many threads concerning > raspberry pi and v8. But there are also so

Re: [v8-users] Re: Cross compiling for raspberry pi

o with cross compiling. > > On Friday, January 9, 2015 at 7:12:14 PM UTC+1, Rodolph Perfetta wrote: >> >> I may be missing something but in your example you are using x64 libs in >> your cross compilation, how could this work? >> >> Rodolph. >> >

Re: [v8-users] ARMv5 Support

That is correct, the base requirement for v8 is ARMv6 with VFPv2. Rodolph. On 11 February 2015 at 14:46, Michael Boldischar < michael.j.boldisc...@gmail.com> wrote: > Is ARMv5 still supported by the V8 engine? I had trouble with NodeJS and > someone suggested that ARMv5 support was dropped by t

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

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

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

ExternalReference(IC_Utility(kKeyedStoreIC_Miss), masm->isolate()); > __ TailCallExternalReference(ref, 3, 1); > > > Would placing it after the __Push() cause some corruption on the stack? > > Separately, I could not find documentation on how to use/run the > built-in arm simulat

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

at the magic instruction is messing up the return > address for that call? My goal is to analyze system behavior when > handling the IC misses, so thats why I placed the instrumentation > there. I could move the instrumentation calls up 1 level or somewhere > else you recommend so that I can e

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

und right, and if so can you suggest how to do it? > > > On Thu, Feb 26, 2015 at 6:57 PM, Rodolph Perfetta > wrote: > > So m5_enableDebugFlag is a function which contains your special > instruction > > followed by a mov pc, lr (standard return). I can see two issues: >

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

ugh the help > messages, I can see options for tracing within the simulator, but > which option actually tells it to actually use it. > > ../out/native/d8 --trace_sim run-deltablue.js > > > > > On Fri, Feb 27, 2015 at 11:28 AM, Rodolph Perfetta > wrote: > > Your

Re: [v8-users] GDB breakpoints in generated ARM code crashing process

I would suggest you use the builtin simulator and its debugger. See https://code.google.com/p/v8-wiki/wiki/ARMDebuggingWithTheSimulator if you have gdb 7 or later, you can also try to build with gdbjit support ('gdbjit=on' on the make command and '--gdbjit' on the d8 command). Rodolph. On Thu, 9

Re: [v8-users] arm erratum support on v8?

Hi, Currently V8 is not affected by the erratum hence the lack of fix. V8 is a very fast moving code base so this may change in the future. If you build V8 form source you must ensure your compiler has the fix though. Regards, Rodolph. On Wed, 17 Jun 2015 at 07:06 Hidenori Yamaji wrote: > Do

Re: [v8-users] arm erratum support on v8?

then 843419 is not happened. > But how about 835769? > > BR, > Hidenori Yamaji > > 2015年6月19日金曜日 2時45分17秒 UTC+9 Rodolph Perfetta: >> >> Hi, >> >> Currently V8 is not affected by the erratum hence the lack of fix. V8 is >> a very fast moving code ba

Re: [v8-users] "Word UnExpected" Error while building v8 on Ubuntu

Hi Johnny, When cross compiling for 32-bit arm you need to explicitly prevent the use of the built-in linker. Simply export GYPFLAGS="-Dlinux_use_bundled_gold=0" You don't need the "-DClang=0" if you define CC, CXX and others. The v8 code base already has a script to cross compile, in the tools d

Re: [v8-users] On Android binary segfaults

from your log it looks like out/android_arm.release/unittests -gtest_list_tests failed can you run the command on its own and see what happens? Rodolph On Sun, 10 Jan 2016 at 20:57 Guillermo Romero wrote: > Hello, > > I'm building V8 for Android (arm), and followed the steps outlined here: > ht

Re: [v8-users] On Android binary segfaults

gmentation fault ./hello-world > root@android:/data/local/tmp/v8 # > > > > > > On Monday, January 11, 2016 at 7:48:47 AM UTC-6, Rodolph Perfetta wrote: > >> from your log it looks like out/android_arm.release/unittests >> -gtest_list_tests failed can you ru