summaryrefslogtreecommitdiffstats
path: root/js/src/jit-test/tests
Commit message (Collapse)AuthorAgeLines
* 1339395 - Part 6: Update jit-tests now that object rest/spread properties ↵Gaming4JC2019-07-18-3/+3
| | | | are a thing.
* 420857 - Part 4: Report the position of opening bracket for missing bracket ↵Gaming4JC2019-07-18-3/+10
| | | | error in array literal.
* 420857 - Part 3: Report the position of opening brace for missing brace ↵Gaming4JC2019-07-18-0/+7
| | | | error in object literal.
* 420857 - Part 2: Report the position of opening brace for missing brace ↵Gaming4JC2019-07-18-0/+46
| | | | error in block.
* 420857 - Part 1: Report the position of opening brace for missing brace ↵Gaming4JC2019-07-18-0/+30
| | | | error in function body.
* 1357506 - Remove assert that constructorBox can only be set once when ↵Gaming4JC2019-07-18-0/+8
| | | | | | | parsing classes. Both asm.js and syntax parsing can abort and rewind parsing of an inner function. The bookkeeping to make sure that a class's constructor FunctionBox is only set once is not worth it -- duplicate constructor definitions already throw an early error.
* 1359622 - Fix assert for calling Function.toString on class constructors ↵Gaming4JC2019-07-18-0/+4
| | | | when the compartment has had source discarded.
* 1340148 - Disallow function redeclarations at module top level.Gaming4JC2019-07-18-0/+94
|
* 104442 - Part 1: Report the position and the kind of previous declaration ↵Gaming4JC2019-07-18-0/+230
| | | | for redeclaration error.
* 1339963 - Part 3: Check IdentifierName in ExportClause without from.Gaming4JC2019-07-18-2/+44
|
* 1336783 - Part 1: Rework on reserved word and remove TokenStream::KeywordIsName.Gaming4JC2019-07-18-3/+1
|
* 1333143 - Self-host Object.prototype.valueOf.Gaming4JC2019-07-18-2/+2
|
* 903389 - Fix uses of ClassMethodIsNative.Gaming4JC2019-07-18-0/+47
|
* 1317374 - Don't do Annex B lexical function behavior when redeclaring a ↵Gaming4JC2019-07-18-1/+3
| | | | parameter name.
* Remove unboxed object tests.wolfbeast2019-06-25-187/+0
|
* Stage 1-4: Update testsTooru Fujisawa2019-02-03-48/+49
|
* Improve graph edge resolution code.wolfbeast2018-10-23-0/+24
| | | | This is a follow-up to ca7ecd37c94e268972697a37eec4e46771c6e6f2 further improving the DiD resolution for CVE-2018-12386.
* Merge remote-tracking branch 'janek/js_regexp_lastindex_1'wolfbeast2018-03-27-2/+2
|\
| * Bug 1317397: Only set lastIndex for global or sticky RegExps in ↵janekptacijarabaci2018-03-24-2/+2
| | | | | | | | RegExpBuiltinExec per ES2017
* | Bug 1357075 - Pad a nop to unwind to the scope just before a destructuring ↵janekptacijarabaci2018-03-25-0/+10
| | | | | | | | | | | | iterator close trynote Issue #74
* | Bug 1342553, Bug 1343072, Bug 1344753 (details in the description)janekptacijarabaci2018-03-25-0/+15
| | | | | | | | | | | | | | | | | | | | Bug 1342553 - Part 0.1: Use try-catch for IteratorClose in for-of Bug 1343072 - Update HasLiveStackValueAtDepth to follow the change in JSTRY_FOR_OF Bug 1344753 - Update for-of stack depth in ControlFlowGenerator::processWhileOrForInLoop Issue #74
* | Bug 1334314 - Fix debug mode OSR exception handling for IteratorClose trynotesjanekptacijarabaci2018-03-25-0/+16
| | | | | | | | Issue #74
* | Bug 1341339 - Check for duplicates in processIteratorsjanekptacijarabaci2018-03-25-0/+9
| | | | | | | | Issue #74
* | Bug 1335996 - Make test for bug 1333946 more reliablejanekptacijarabaci2018-03-25-3/+5
| | | | | | | | Issue #74
* | Bug 1333946 - Make IonBuilder::processIterators transitivejanekptacijarabaci2018-03-25-0/+6
| | | | | | | | Issue #74
* | Bug 1331444 - Keep iterators alive in Ion in for-of loops for IteratorClose ↵janekptacijarabaci2018-03-25-0/+7
|/ | | | | | due to exceptions Issue #74
* Add support for the function `name` property.wolfbeast2018-03-20-22/+22
|\ | | | | | | | | | | This resolves #78. Merged remote-tracking branch 'janek/js_function_name_1'
| * Part 4: Fix existing testsjanekptacijarabaci2018-03-19-22/+22
| | | | | | | | Issue #87
* | Bug 1323868: Report object allocation failure when running off-main-threadjanekptacijarabaci2018-03-19-0/+5
|/ | | | | Issue #77 [Depends on] Bug 1192038: RegExp.prototype should be an ordinary object
* Support ES6's "new function" constructwolfbeast2018-03-18-12/+8
|\ | | | | | | | | | | This resolves #75. Merged remote-tracking branch 'janek/js_function_new_1'
| * Bug 755821: Function() should use the parser's argument parsing codejanekptacijarabaci2018-03-16-12/+8
| |
* | Handle same-compartment wrappers in TypedArray methods.wolfbeast2018-03-17-0/+20
|/ | | | | | | | | | | | | | | | | | | | | | CallTypedArrayMethodIfWrapped (and the CallNonGeneric machinery throughout the engine) unwraps the `this` argument, but the other arguments are only rewrapped for the target compartment. The pattern being used before this patch to get the length of a TypedArray or possible TypedArray wrapper is: `callFunction(CallTypedArrayMethodIfWrapped, O, O, "TypedArrayLength")` The first `O` is the `this` value and the second is an argument. If `O` is a cross-compartment wrapper, this works fine. The first `O` is unwrapped, revealing the actual TypedArray object; the second `O` is rewrapped for that TypedArray's compartment, producing the same TypedArray. However, if `O` is a same-compartment wrapper, this doesn't work. The first `O` is unwrapped, revealing the actual TypedArray object in the same compartment; rewrapping the other `O` does nothing to it, since it is already an object in the target compartment. Thus TypedArrayLength receives a `this` value that's an unwrapped TypedArray, but an argument that is still a wrapper. The fix is to have CallTypedArrayMethodIfWrapped targets only expect `this` to be an unwrapped TypedArray.
* Add rematerialized frames to the table on JitActivation after ↵wolfbeast2018-02-08-0/+65
| | | | rematerialization succeeds.
* Remove VerifyBarriers() and MaybeVerifyBarriers() stubs and callers.wolfbeast2018-02-03-5/+0
|
* Add m-esr52 at 52.6.0Matt A. Tobin2018-02-02-0/+188348
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-10 19:21:25 +0000