Commit message (Collapse) | Author | Age | Lines | |
---|---|---|---|---|
* | Remove JSOP_SPREADCALLARRAY and just use JSOP_NEWARRAY again. | wolfbeast | 2019-06-18 | -25/+9 |
| | ||||
* | Update comment | wolfbeast | 2019-06-18 | -4/+2 |
| | ||||
* | Remove and clean up more code. | wolfbeast | 2019-06-18 | -88/+26 |
| | ||||
* | Replace SetOrExtendBoxedOrUnboxedDenseElements with direct calls. | wolfbeast | 2019-06-18 | -77/+70 |
| | ||||
* | Clean up and rename MoveBoxedOrUnboxedDenseElements. | wolfbeast | 2019-06-18 | -22/+19 |
| | ||||
* | Convert CopyBoxedOrUnboxedDenseElements to something that doesn't crash. | wolfbeast | 2019-06-17 | -23/+33 |
| | ||||
* | Fix typo in ArrayShiftMoveElements | wolfbeast | 2019-06-17 | -1/+1 |
| | ||||
* | Remove functors for array natives. | wolfbeast | 2019-06-12 | -230/+59 |
| | ||||
* | Remove unboxed array context option and shell flag. | wolfbeast | 2019-06-12 | -25/+0 |
| | ||||
* | Remove unused LIR temp register for unboxed arrays. | wolfbeast | 2019-06-12 | -28/+12 |
| | ||||
* | Make use of ArrayObjects in favor of generic JS objects. | wolfbeast | 2019-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. | wolfbeast | 2019-06-10 | -224/+115 |
| | ||||
* | Merge branch 'master' into remove-unboxed | wolfbeast | 2019-06-08 | -34/+212 |
|\ | ||||
| * | Fix #1091 deprot | wolfbeast | 2019-05-29 | -0/+2 |
| | | ||||
| * | Improve efficiency of (C++) heap allocations related to | wolfbeast | 2019-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 Hansen | 2019-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 PPC64 | wolfbeast | 2019-05-25 | -1/+1 |
| | | | | | | | | Fixes #1092 | |||
| * | Merge pull request #1091 from MoonchildProductions/remove-unboxed | Moonchild | 2019-05-22 | -1510/+102 |
| |\ | | | | | | | Remove unboxed objects phase 1 | |||
| * | | Implement Symbol.prototype.description | wolfbeast | 2019-05-20 | -0/+33 |
| | | | | | | | | | | | | Resolves #1096 | |||
| * | | Implement array.flat and array.flatMap | wolfbeast | 2019-05-19 | -1/+120 |
| | | | | | | | | | | | | | | | | | | Self-hosted implementation that adds both functions and adds them to @@unscopables as specced in ES2019. Resolves #1095 | |||
| * | | Implement String.prototype.trimStart and trimEnd. | wolfbeast | 2019-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 2 | wolfbeast | 2019-05-23 | -1611/+124 |
| | | | ||||
* | | | Remove UnboxedArray code part 1 | wolfbeast | 2019-05-23 | -1231/+251 |
| |/ |/| | ||||
* | | Remove Unboxed Objects from vm/ - Part 2 | wolfbeast | 2019-05-16 | -64/+17 |
| | | ||||
* | | Remove unboxed object code from jit, Part 1 | wolfbeast | 2019-05-16 | -627/+26 |
| | | ||||
* | | Remove Unboxed Objects from vm/ Part 1 + fix deprot | wolfbeast | 2019-05-16 | -15/+10 |
| | | ||||
* | | Remove array header | wolfbeast | 2019-05-16 | -1/+0 |
| | | ||||
* | | Remove unboxed object code from iteration. | wolfbeast | 2019-05-15 | -32/+10 |
| | | ||||
* | | Remove unboxed objects from GC | wolfbeast | 2019-05-15 | -118/+3 |
| | | ||||
* | | Remove Unboxed Objects in ScalarReplacement | wolfbeast | 2019-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 2 | wolfbeast | 2019-05-15 | -12/+0 |
| | | ||||
* | | remove unboxed code chunk (wip1) | wolfbeast | 2019-05-14 | -507/+25 |
| | | ||||
* | | Unhook Unboxed Objects option | wolfbeast | 2019-05-13 | -23/+12 |
|/ | ||||
* | Braces and one more typo fix for comment | win7-7 | 2019-04-30 | -3/+5 |
| | ||||
* | Whitespaces, typo, tabs to space | win7-7 | 2019-04-30 | -7/+7 |
| | | | Remove whitespaces, correct comment typo, one more tab to space | |||
* | Remove rest of empty lines. | win7-7 | 2019-04-30 | -3/+1 |
| | ||||
* | Remove some empty lines | win7-7 | 2019-04-30 | -7/+0 |
| | ||||
* | Remaining tabs to spaces JavaScriptShared.cpp | win7-7 | 2019-04-30 | -4/+4 |
| | ||||
* | remaining tabs to space js/src/jsgc.cpp | win7-7 | 2019-04-30 | -26/+26 |
| | ||||
* | tab to spaces js/ipc | win7-7 | 2019-04-30 | -2/+2 |
| | ||||
* | tab to spaces js/src/gc | win7-7 | 2019-04-30 | -21/+21 |
| | ||||
* | tab to spaces js/src | win7-7 | 2019-04-30 | -46/+46 |
| | ||||
* | Add newline at end of files | win7-7 | 2019-04-29 | -3/+3 |
| | ||||
* | Add newline at end of file js/src/builtin | win7-7 | 2019-04-29 | -1/+1 |
| | ||||
* | add newline at end of files js/src/gc | win7-7 | 2019-04-29 | -4/+4 |
| | ||||
* | Add newline at end of files js/src | win7-7 | 2019-04-29 | -3/+3 |
| | ||||
* | Space to comment. | win7-7 | 2019-04-29 | -0/+1 |
| | ||||
* | Improve dead compartment collection js/ipc | win7-7 | 2019-04-29 | -4/+14 |
| | ||||
* | Improve dead compartment collection js/src/builtin | win7-7 | 2019-04-29 | -7/+5 |
| | ||||
* | Improve dead compartment collection js/src/gc | win7-7 | 2019-04-29 | -8/+32 |
| |