safe compiler opts for ARM?

11 views
Skip to first unread message

CoolAJ86

unread,
Dec 15, 2010, 6:22:13 PM12/15/10
to v8-users
I'm building V8 2.3.8 natively on ARM and it keeps segfaulting every
few minutes of runtime (Node.JS).


These are the compiler opts that I have set. Are any of these
incompatible / unsafe to use with V8?

export CC_OPTS="-ggdb3"
export TARGET_ARCH="-march=armv7-a" # must be at least armv5te
export TARGET_TUNE="-mtune=cortex-a8 -mfpu=neon -mfloat-abi=softfp -
mthumb-interwork -mno-thumb" # optional


export CCLD="gcc ${CC_OPTS} ${TARGET_ARCH} ${TARGET_TUNE}"
export CC="gcc ${CC_OPTS} ${TARGET_ARCH} ${TARGET_TUNE}"
export CXX="g++ ${CC_OPTS} ${TARGET_ARCH} ${TARGET_TUNE}"

./configure
make
make install




I'm getting messages like this

Program received signal SIGSEGV, Segmentation fault.
0x001794d8 in
v8::internal::StringDictionary::FindEntry(v8::internal::String*) ()
Current language: auto
The current source language is "auto; currently asm".
(gdb) bt
#0 0x001794d8 in
v8::internal::StringDictionary::FindEntry(v8::internal::String*) ()
#1 0x0017a52c in
v8::internal::JSObject::LocalLookupRealNamedProperty(v8::internal::String*,
v8::internal::LookupResult*) ()
#2 0x0014a68c in
v8::internal::StoreIC::Store(v8::internal::InlineCacheState,
v8::internal::Handle<v8::internal::Object>,
v8::internal::Handle<v8::internal::String>,
v8::internal::Handle<v8::internal::Object>) ()
#3 0x0014a9a0 in v8::internal::StoreIC_Miss(v8::internal::Arguments)
()
#4 0x42526254 in ?? ()
#5 0x42526254 in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt
stack?)




and this

Program received signal SIGSEGV, Segmentation fault.
0x001454e4 in
v8::internal::Heap::CopyJSObject(v8::internal::JSObject*) ()
Current language: auto
The current source language is "auto; currently asm".
(gdb) bt
#0 0x001454e4 in
v8::internal::Heap::CopyJSObject(v8::internal::JSObject*) ()
#1 0x001b041c in
v8::internal::Runtime_CreateObjectLiteralShallow(v8::internal::Arguments)
()
#2 0x4250c254 in ?? ()
#3 0x4250c254 in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt
stack?)

Erik Corry

unread,
Dec 17, 2010, 4:36:45 AM12/17/10
to v8-u...@googlegroups.com
16. dec. 2010 00.22 skrev CoolAJ86 <cool...@gmail.com>:
> I'm building V8 2.3.8 natively on ARM and it keeps segfaulting every
> few minutes of runtime (Node.JS).
>
>
> These are the compiler opts that I have set. Are any of these
> incompatible / unsafe to use with V8?
>
> export CC_OPTS="-ggdb3"
> export TARGET_ARCH="-march=armv7-a" # must be at least armv5te
> export TARGET_TUNE="-mtune=cortex-a8 -mfpu=neon -mfloat-abi=softfp -
> mthumb-interwork -mno-thumb" # optional

I would normally expect -mfpu=vfp, but I don't think that changes the
ABI so it's probably not your problem.

Can you reproduce the problem in standalone V8 without node? Try

/path/to/v8/tools/test.py --mode=release --snapshot --arch=arm -j2

and again with mode=debug.

> --
> v8-users mailing list
> v8-u...@googlegroups.com
> http://groups.google.com/group/v8-users
>

--
Erik Corry, Software Engineer
Google Denmark ApS - Frederiksborggade 20B, 1 sal,
1360 København K - Denmark - CVR nr. 28 86 69 84

Reply all
Reply to author
Forward
0 new messages