Commit message (Collapse) | Author | Age | Lines | |
---|---|---|---|---|
* | Add Atomics.notify instead of Atomics.wake according to revised spec. | wolfbeast | 2019-06-12 | -29/+30 |
| | | | | | - Keep .wake as an alias until we're certain it can be removed. - Enable SAB memory | |||
* | 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 | -1506/+102 |
|\ | | | | | Remove unboxed objects phase 1 | |||
| * | 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 | -19/+12 |
| | | ||||
* | | Implement Symbol.prototype.description | wolfbeast | 2019-05-20 | -0/+33 |
| | | | | | | | | Resolves #1096 | |||
* | | Implement array.flat and array.flatMap | wolfbeast | 2019-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. | 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 | |||
* | 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 space js/src/jsgc.cpp | win7-7 | 2019-04-30 | -26/+26 |
| | ||||
* | 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 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/src/builtin | win7-7 | 2019-04-29 | -7/+5 |
| | ||||
* | Improve dead compartment collection js/src/gc | win7-7 | 2019-04-29 | -8/+32 |
| | ||||
* | Improve dead compartment collection js/src | win7-7 | 2019-04-29 | -91/+141 |
| | ||||
* | Remove useless assert. | wolfbeast | 2019-04-25 | -1/+0 |
| | | | | Resolves #1055. | |||
* | Rename TokenStream::reportStrictWarningErrorNumberVA to | wolfbeast | 2019-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. | wolfbeast | 2019-04-06 | -27/+0 |
| | ||||
* | Inline Parser::reportHelper into its callers. | wolfbeast | 2019-04-06 | -8/+29 |
| | ||||
* | Remove Parser::reportWithNode and its remaining callers. | wolfbeast | 2019-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 using | wolfbeast | 2019-04-06 | -30/+27 |
| | | | | explicitly-specified offsets. | |||
* | Simplify checking of targets within destructuring patterns. | wolfbeast | 2019-04-06 | -82/+14 |
| | ||||
* | Simplify increment/decrement operand checking. | wolfbeast | 2019-04-06 | -18/+20 |
| | ||||
* | Inline Parser::checkAssignmentToCall into its sole caller. | wolfbeast | 2019-04-06 | -16/+5 |
| | ||||
* | Specify an explicit offset when reporting an error for a for-of loop | wolfbeast | 2019-04-06 | -1/+1 |
| | | | | whose target is an expression that begins with 'let'. | |||
* | Simplify checking of the left-hand side of assignment and compound | wolfbeast | 2019-04-06 | -50/+28 |
| | | | | assignment expressions. | |||
* | Remove for-in/of loop parsing code that redundantly marks the loop | wolfbeast | 2019-04-06 | -6/+0 |
| | | | | target as assigned -- Parser::forHeadStart already does this. | |||
* | Report some errors about invalid left-hand-sides in for-in/of loop heads | wolfbeast | 2019-04-06 | -38/+26 |
| | | | | using code with an explicitly computed offset. | |||
* | Report the error for uninitialized const-declaration in for(;;) loop | wolfbeast | 2019-04-06 | -1/+1 |
| | | | | head using an explicit offset. | |||
* | Remove Parser::reportWithOffset since it's no longer used. | wolfbeast | 2019-04-06 | -12/+0 |
| | ||||
* | Introduce Parser::warningAt | wolfbeast | 2019-04-06 | -12/+19 |
| | | | | | This reduces reporting an warning at a particular offset to its bare essentials, simplifying calls. | |||
* | Report for-loop-decl-with-initializer errors using a specified offset | wolfbeast | 2019-04-06 | -2/+4 |
| | | | | instead of a node's offset. |