Updates:
Status: Fixed
Comment #8 on issue 1018 by sgje...@chromium.org: Fatal error in ARM
crankshaft: Invalid gap size.
http://code.google.com/p/v8/issues/detail?id=1018
(No comment was entered for this change.)
--
v8-dev mailing list
v8-dev@googlegroups.com
http://groups.google.co
Updates:
Status: Assigned
Owner: sgje...@chromium.org
Comment #7 on issue 1018 by sgje...@chromium.org: Fatal error in ARM
crankshaft: Invalid gap size.
http://code.google.com/p/v8/issues/detail?id=1018
(No comment was entered for this change.)
--
v8-dev mailing list
v8-dev@g
Issue 1018: Fatal error in ARM crankshaft: Invalid gap size.
http://code.google.com/p/v8/issues/detail?id=1018
This issue is no longer blocking issue 1032.
See http://code.google.com/p/v8/issues/detail?id=1032
--
You received this message because you are listed in the owner
or CC fields of this i
Comment #6 on issue 1018 by a...@chromium.org: Fatal error in ARM
crankshaft: Invalid gap size.
http://code.google.com/p/v8/issues/detail?id=1018
I think that is it. I put in tracing of emitting constant pool, parallel
move and the place where the offset is too big:
BeginDoParallelMove
Em
Comment #5 on issue 1018 by a...@chromium.org: Fatal error in ARM
crankshaft: Invalid gap size.
http://code.google.com/p/v8/issues/detail?id=1018
Thinking out loud: could this be caused by emitting a constant pool while
generating the code for a gap?
--
v8-dev mailing list
v8-dev@googlegr
Updates:
Labels: HW-ARM
Comment #4 on issue 1018 by sgje...@chromium.org: Fatal error in ARM
crankshaft: Invalid gap size.
http://code.google.com/p/v8/issues/detail?id=1018
(No comment was entered for this change.)
--
v8-dev mailing list
v8-dev@googlegroups.com
http://groups.google.c
Comment #3 on issue 1018 by karlkl...@chromium.org: Fatal error in ARM
crankshaft: Invalid gap size.
http://code.google.com/p/v8/issues/detail?id=1018
shell_g --nocrankshaft --enable-slow-asserts --debug-code --verify-heap
test/../tools/splaytree.js test/../tools/codemap.js
test/../tools/
Comment #2 on issue 1018 by karlkl...@chromium.org: Fatal error in ARM
crankshaft: Invalid gap size.
http://code.google.com/p/v8/issues/detail?id=1018
For this function:
0xf7fd435d: [SharedFunctionInfo]
- name: 0xf5bea2c9
- expected_nof_properties: 10
- instance class name = #Object
- c
Comment #1 on issue 1018 by karlkl...@chromium.org: Fatal error in ARM
crankshaft: Invalid gap size.
http://code.google.com/p/v8/issues/detail?id=1018
#0 0xf7fdf430 in __kernel_vsyscall ()
#1 0xf7d37921 in raise (sig=6)
at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
#2 0xf7d3ad52 in abor
