Bug 44244

Summary: [INTERPRETER] Two Sputnik tests fail to encode two-byte unicode character (\u2028)
Product: WebKit Reporter: David Kilzer (:ddkilzer) <ddkilzer>
Component: JavaScriptCoreAssignee: Nobody <webkit-unassigned>
Status: RESOLVED WORKSFORME    
Severity: Normal CC: barraclough, ggaren, oliver
Priority: P2 Keywords: InRadar
Version: 528+ (Nightly build)   
Hardware: Mac   
OS: OS X 10.6   

David Kilzer (:ddkilzer)
Reported 2010-08-19 04:41:41 PDT
Two Sputnik tests fail on the JSC interpreter when encoding a two-byte unicode character (\u2028), but pass on the JSC JIT: fast/js/sputnik/Conformance/15_Native_Objects/15.10_RegExp/15.10.2/15.10.2.12_CharacterClassEscape/S15.10.2.12_A1_T2.html fast/js/sputnik/Conformance/15_Native_Objects/15.10_RegExp/15.10.2/15.10.2.12_CharacterClassEscape/S15.10.2.12_A2_T2.html --- a/LayoutTests/fast/js/sputnik/Conformance/15_Native_Objects/15.10_RegExp/15.10.2/15.10.2.12_CharacterClassEscape/S15.10.2.12_A1_T2-expected.txt +++ b/LayoutTests/fast/js/sputnik/Conformance/15_Native_Objects/15.10_RegExp/15.10.2/15.10.2.12_CharacterClassEscape/S15.10.2.12_A1_T2-expected.txt @@ -1,6 +1,6 @@ S15.10.2.12_A1_T2 -PASS +FAIL SputnikError: #3: var arr = /\s/.exec("\u2028"); arr[0] === "\u2028". Actual. null TEST COMPLETE --- a/LayoutTests/fast/js/sputnik/Conformance/15_Native_Objects/15.10_RegExp/15.10.2/15.10.2.12_CharacterClassEscape/S15.10.2.12_A2_T2-expected.txt +++ b/LayoutTests/fast/js/sputnik/Conformance/15_Native_Objects/15.10_RegExp/15.10.2/15.10.2.12_CharacterClassEscape/S15.10.2.12_A2_T2-expected.txt @@ -1,6 +1,6 @@ S15.10.2.12_A2_T2 -PASS +FAIL SputnikError: #3: var arr = /\S/.exec("\u2028"); arr[0] === "\u2028". Actual. ‚Ä® TEST COMPLETE
Attachments
David Kilzer (:ddkilzer)
Comment 1 2010-08-19 04:48:31 PDT
Gavin Barraclough
Comment 2 2011-06-10 19:17:33 PDT
From testing on desktop interpreter builds, I'm no longer seeing functional differences to the JIT. This is likely predominantly due to replacing PCRE with YARR, along with other recent bug fixes.
Note You need to log in before you can comment on or make changes to this bug.