summaryrefslogtreecommitdiffstats
path: root/js/src
Commit message (Collapse)AuthorAgeLines
* Replace SetOrExtendBoxedOrUnboxedDenseElements with direct calls.wolfbeast2019-06-14-77/+70
|
* Clean up and rename MoveBoxedOrUnboxedDenseElements.wolfbeast2019-06-13-22/+19
|
* Convert CopyBoxedOrUnboxedDenseElements to calls to initDenseElementwolfbeast2019-06-13-27/+13
|
* Remove functors for array natives.wolfbeast2019-06-12-230/+59
|
* Remove unboxed array context option and shell flag.wolfbeast2019-06-12-25/+0
|
* Remove unused LIR temp register for unboxed arrays.wolfbeast2019-06-12-28/+12
|
* Make use of ArrayObjects in favor of generic JS objects.wolfbeast2019-06-12-96/+57
| | | | | ArrayObjects has been a thing for years but been under-used. About time they are used where prudent.
* Inline combined methods for NativeObject and UnboxedArrayObject accesses.wolfbeast2019-06-10-224/+115
|
* Merge branch 'master' into remove-unboxedwolfbeast2019-06-08-33/+211
|\
| * Fix #1091 deprotwolfbeast2019-05-29-0/+2
| |
| * Improve efficiency of (C++) heap allocations related towolfbeast2019-05-28-14/+24
| | | | | | | | | | | | BytecodeEmitter::code. While there, also add some sanity checks and clean up code.
| * [js, ARM] Always check error return from BufferOffset::diffB.Lars T Hansen2019-05-25-2/+10
| | | | | | | | | | | | | | We were missing error checks at two points. In one case an error return is meaningful; in another case it is not, as the problem should have been guarded against at a higher level by emitting far jump islands soon enough during pasteup of compiled code.
| * Fix architecture flag for PPC64wolfbeast2019-05-25-1/+1
| | | | | | | | Fixes #1092
| * Merge pull request #1091 from MoonchildProductions/remove-unboxedMoonchild2019-05-22-1506/+102
| |\ | | | | | | Remove unboxed objects phase 1
| * | Implement Symbol​.prototype​.descriptionwolfbeast2019-05-20-0/+33
| | | | | | | | | | | | Resolves #1096
| * | Implement array.flat and array.flatMapwolfbeast2019-05-19-0/+119
| | | | | | | | | | | | | | | | | | Self-hosted implementation that adds both functions and adds them to @@unscopables as specced in ES2019. Resolves #1095
| * | Implement String.prototype.trimStart and trimEnd.wolfbeast2019-05-17-16/+22
| | | | | | | | | | | | | | | | | | This renames our internal function names because *Left and *Right might be deprecated and have to be removed later, making that trivial. Resolves #1089
* | | Remove UnboxedArray code part 2wolfbeast2019-05-23-1611/+124
| | |
* | | Remove UnboxedArray code part 1wolfbeast2019-05-23-1231/+251
| |/ |/|
* | Remove Unboxed Objects from vm/ - Part 2wolfbeast2019-05-16-64/+17
| |
* | Remove unboxed object code from jit, Part 1wolfbeast2019-05-16-627/+26
| |
* | Remove Unboxed Objects from vm/ Part 1 + fix deprotwolfbeast2019-05-16-15/+10
| |
* | Remove array headerwolfbeast2019-05-16-1/+0
| |
* | Remove unboxed object code from iteration.wolfbeast2019-05-15-32/+10
| |
* | Remove unboxed objects from GCwolfbeast2019-05-15-118/+3
| |
* | Remove Unboxed Objects in ScalarReplacementwolfbeast2019-05-15-112/+0
| | | | | | | | | | | | | | | | | | A note about the Scalar Replacement Changes: The M{Load,Store}Unboxed* instructions in theory could be used to manipulate and analyze typed arrays. However, TypedArrays should already be excluded from eligibility because of the potential for cross-thread sharing in a SharedArrayBuffer world, and so the only support in Scalar Replacement here is for Unboxed Objects, meaning it can all be removed.
* | Remove initial chunk of Unboxed Objects machinery part 2wolfbeast2019-05-15-12/+0
| |
* | remove unboxed code chunk (wip1)wolfbeast2019-05-14-507/+25
| |
* | Unhook Unboxed Objects optionwolfbeast2019-05-13-19/+12
|/
* Braces and one more typo fix for commentwin7-72019-04-30-3/+5
|
* Whitespaces, typo, tabs to spacewin7-72019-04-30-7/+7
| | | Remove whitespaces, correct comment typo, one more tab to space
* Remove rest of empty lines.win7-72019-04-30-3/+1
|
* Remove some empty lineswin7-72019-04-30-7/+0
|
* remaining tabs to space js/src/jsgc.cppwin7-72019-04-30-26/+26
|
* tab to spaces js/src/gcwin7-72019-04-30-21/+21
|
* tab to spaces js/srcwin7-72019-04-30-46/+46
|
* Add newline at end of file js/src/builtinwin7-72019-04-29-1/+1
|
* add newline at end of files js/src/gcwin7-72019-04-29-4/+4
|
* Add newline at end of files js/srcwin7-72019-04-29-3/+3
|
* Space to comment.win7-72019-04-29-0/+1
|
* Improve dead compartment collection js/src/builtinwin7-72019-04-29-7/+5
|
* Improve dead compartment collection js/src/gcwin7-72019-04-29-8/+32
|
* Improve dead compartment collection js/srcwin7-72019-04-29-91/+141
|
* Remove useless assert.wolfbeast2019-04-25-1/+0
| | | | Resolves #1055.
* Rename TokenStream::reportStrictWarningErrorNumberVA towolfbeast2019-04-06-10/+9
| | | | | | | TokenStream::reportExtraWarningErrorNumberVA for clarity. Emit Extra Warnings instead of Strict Warnings from the BCE where it makes sense.
* Remove Parser::reportHelper since it's no longer used.wolfbeast2019-04-06-27/+0
|
* Inline Parser::reportHelper into its callers.wolfbeast2019-04-06-8/+29
|
* Remove Parser::reportWithNode and its remaining callers.wolfbeast2019-04-06-24/+7
| | | | | All of the callsites have a full ParseNode* at hand, of which the offset can be directly accessed.
* Report errors for bad increment/decrement operands usingwolfbeast2019-04-06-30/+27
| | | | explicitly-specified offsets.
* Simplify checking of targets within destructuring patterns.wolfbeast2019-04-06-82/+14
|
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-26 16:04:26 +0000