It would be interesting to run

gdb --args chromium/chromium/src/out/Debug/mksnapshot"
"/home/vish/work/chromium/
chromium/src/out/Debug/obj.target/geni/snapshot.cc"

and find out what the illegal instruction was.  This could be a
compiler issue (are you on gcc-4.4?) or it could be a genuine illegal
instruction issue.  I don't think V8 gets much testing on such old
CPUs.

2009/11/21 slowpoison <[email protected]>:
>
> Here's what happens when I fire a Chrome make:
>
>  g++ -pthread -m32 -rdynamic -o out/Debug/mksnapshot -Wl,--start-group
> out/Debug/obj.target/mksnapshot/v8/src/mksnapshot.o out/Debug/
> obj.target/v8/tools/gyp/libv8_nosnapshot.a out/Debug/obj.target/v8/
> tools/gyp/libv8_base.a -Wl,--end-group -lrt
>  export LD_LIBRARY_PATH=/home/vish/work/chromium/chromium/src/out/
> Debug/lib.host:/home/vish/work/chromium/chromium/src/out/Debug/
> lib.target:$LD_LIBRARY_PATH; cd v8/tools/gyp; mkdir -p /home/vish/work/
> chromium/chromium/src/out/Debug/obj.target/geni; "/home/vish/work/
> chromium/chromium/src/out/Debug/mksnapshot" "/home/vish/work/chromium/
> chromium/src/out/Debug/obj.target/geni/snapshot.cc"
> Illegal instruction
> make: *** [out/Debug/obj.target/geni/snapshot.cc] Error 132
>
>
> I have included cpuinfo below:
> src> cat /proc/cpuinfo
> processor       : 0
> vendor_id       : GenuineIntel
> cpu family      : 6
> model           : 8
> model name      : Pentium III (Coppermine)
> stepping        : 6
> cpu MHz         : 930.174
> cache size      : 256 KB
> fdiv_bug        : no
> hlt_bug         : no
> f00f_bug        : no
> coma_bug        : no
> fpu             : yes
> fpu_exception   : yes
> cpuid level     : 2
> wp              : yes
> flags           : fpu vme de pse tsc msr pae mce cx8 mtrr pge mca cmov pse36
> mmx fxsr sse up
> bogomips        : 1860.34
> clflush size    : 32
> power management:
>
> >
>

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

Reply via email to