Bug 47763 - Arguments.length errors on JSVALUE32 JIT (MIPS and x86)
Summary: Arguments.length errors on JSVALUE32 JIT (MIPS and x86)
Status: RESOLVED INVALID
Alias: None
Product: WebKit
Classification: Unclassified
Component: JavaScriptCore (show other bugs)
Version: 528+ (Nightly build)
Hardware: Other Linux
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-10-15 22:40 PDT by Chao-ying Fu
Modified: 2010-10-19 20:38 PDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Chao-ying Fu 2010-10-15 22:40:56 PDT 
Hi All,

  I try JSVALUE32 JIT on MIPS and X86, and there are same failures when accessing arguments.length.  Please check the following.  Thanks!
Ex:
chao-ying-fus-macbook:Release icebergfu$ ./jsc 
> function a() { return arguments.length;}
undefined
> a()
0
> a(1)
null
> a(1,2)
1
> a(1,2,3)
Segmentation fault

Regards,
Chao-ying
Comment 1 Oliver Hunt 2010-10-17 14:25:15 PDT 
JSVALUE32 is not a valid build configuration on any platform anymore.  I'm surprised jsc works at all when you enable it.
Comment 2 Chao-ying Fu 2010-10-18 10:29:41 PDT 
For X86 build, I put "#define WTF_USE_JSVALUE32 1" in Platform.h to test it.

For MIPS build, I use "./WebKitTools/Scripts/build-webkit --qt DEFINES+=WTF_USE_JSVALUE32=1" to test it.  There are four errors as follows. (I think these errors are from wrong "arguments.length".)
Ex:
ecma/ExecutionContexts/10.1.8-1.js
ecma/ExecutionContexts/10.1.8-2.js
ecma_3/ExecutionContexts/10.1.3-1.js
ecma_3/Expressions/11.6.1-1.js


If JSVALUE32 is not supported any more in jsc, then just ignore this bug.
Thanks!

Regards,
Chao-ying
Comment 3 Alexey Proskuryakov 2010-10-19 20:38:34 PDT 
JSVALUE32 has been removed in bug 47948 (today).