summaryrefslogtreecommitdiffstats
path: root/js/src/jit-test/tests
Commit message (Collapse)AuthorAgeLines
* Part 4: Fix existing testsjanekptacijarabaci2018-03-19-22/+22
| | | | Issue #87
* 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