2009/9/9 Rames <[email protected]>:
>
> In my hurry I didn't read your answers properly. Sorry for that.
>
> My cpu is a Cortex A8 with an ARMv7-a version architecture and my gcc
> compiler uses    #define __ARM_ARCH_4T__ 1 .

Your gcc is designed by default to compile things that work with a
wide variety of ARM chips. V8 should work even with these pessimistic
assumptions, but you can't compile the VM in Thumb mode on such an old
chip.  But as you note below you can use the -march flag to compile
for newer CPUs if you know you won't be running on such old hardware.

> The patch you gave me didnt change the compile errors.
> I really don't know about ARM Instruction Set versions, but I hope
> this might help you to fix a potential bug.
>
> Actually my problem is not to compile on the board itself, but rather
> to be sure that my tests results are accurate and it could be solved
> more easily if can you confirm me I can trust the cross-compiled shell
> obtained the following way:
>
> 1) Modifying the v8 SConstruct adding    'CCFLAGS':      ['-
> march=armv7-a']    to the arm architecture (line 162)
> 2) Exporting my environment variables CC, CXX, AR, AS, RANLIB, LD to
> my CodeSourcery crosstools (arm-none-linux-gnueabi-gcc , etc)
> 3) Cross-compiling with     scons arch=arm sample=shell
> 4) Running the cross-compiled shell on my cpu

That sounds fine and should give you a VM that works.  To be certain,
there are some tests that are bundled with the VM source that you can
run with the test.py script.  See
http://code.google.com/p/v8/wiki/Testing  At the moment we pass all
tests on ARM apart from some debug tests.  There's a way to tell
test.py to use the ARM test expectations, but I can't remember it
right now.

-- 
Erik Corry, Software Engineer
Google Denmark ApS.  CVR nr. 28 86 69 84
c/o Philip & Partners, 7 Vognmagergade, P.O. Box 2227, DK-1018
Copenhagen K, Denmark.

--~--~---------~--~----~------------~-------~--~----~
v8-users mailing list
[email protected]
http://groups.google.com/group/v8-users
-~----------~----~----~----~------~----~------~--~---

Reply via email to