summaryrefslogtreecommitdiffstats
path: root/js/src
Commit message (Collapse)AuthorAgeLines
* Issue #1142 - Cleanup unused debug code for unboxed objectsGaming4JC2019-06-28-8/+1
| | | | Also fixes an assertion during compile if debug is enabled since unboxed objects have been removed.
* Issue #1142 - Remove uneeded assertion (#1145)g4jc2019-06-28-1/+0
| | | Since unboxed objects were removed, isUnboxed is undefined. This causes a build failure when debuging is enabled. This patch fixes the issue by removing the uneeeded assertion.
* Add StoreBuffer-inl.h header to jsobj.cppTravis W2019-06-27-0/+1
| | | This should fix deprot on the Linux and Macintosh
* Remove anyNewScript()wolfbeast2019-06-26-12/+3
|
* Clean up MObjectStatewolfbeast2019-06-26-59/+6
|
* Remove now-unused parameter (prev. used for unboxed objects).wolfbeast2019-06-26-10/+6
|
* Remove UnboxedObjects ObjectGroup addendumwolfbeast2019-06-25-36/+7
|
* Remove unboxed object tests.wolfbeast2019-06-25-187/+0
|
* Remove Unboxed Objects Option Codewolfbeast2019-06-25-8/+0
|
* Remove Unboxed Object code from /vm, Part 3.wolfbeast2019-06-25-1560/+13
|
* Remove Unboxed Object code from jit, Part 4.wolfbeast2019-06-25-406/+20
|
* Remove Unboxed Object code from jit, Part 3.wolfbeast2019-06-23-85/+10
|
* Fix unified deprotwolfbeast2019-06-23-1/+2
|
* Remove Unboxed Object code from jit, Part 2.wolfbeast2019-06-23-1048/+9
|
* Call a more generic function when inlining array natives.wolfbeast2019-06-20-26/+5
| | | | | | | This simplifies the code a bit because ElementAccessHasExtraIndexedProperty checks for length-overflow (directly) and sparse-indexes (through TypeCanHaveExtraIndexedProperties) so the callers don't have to do that anymore.
* Merge pull request #1137 from MoonchildProductions/remove-unboxed-checkedMoonchild2019-06-19-3555/+633
|\ | | | | Remove unboxed (checked branch)
| * Tabs -> Spaces (no code change)wolfbeast2019-06-18-4/+4
| |
| * Remove/inline CanonicalizeArrayLengthValue.wolfbeast2019-06-18-29/+14
| |
| * Remove JSOP_SPREADCALLARRAY and just use JSOP_NEWARRAY again.wolfbeast2019-06-18-25/+9
| |
| * Update commentwolfbeast2019-06-18-4/+2
| |
| * Remove and clean up more code.wolfbeast2019-06-18-88/+26
| |
| * Replace SetOrExtendBoxedOrUnboxedDenseElements with direct calls.wolfbeast2019-06-18-77/+70
| |
| * Clean up and rename MoveBoxedOrUnboxedDenseElements.wolfbeast2019-06-18-22/+19
| |
| * Convert CopyBoxedOrUnboxedDenseElements to something that doesn't crash.wolfbeast2019-06-17-23/+33
| |
| * Fix typo in ArrayShiftMoveElementswolfbeast2019-06-17-1/+1
| |
| * 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
| |\
| * | Remove UnboxedArray code part 2wolfbeast2019-05-23-1611/+124
| | |
| * | Remove UnboxedArray code part 1wolfbeast2019-05-23-1231/+251
| | |
* | | Update tzdata SpiderMonkey fileswolfbeast2019-06-15-6/+7
| | |
* | | Add Atomics.notify instead of Atomics.wake according to revised spec.wolfbeast2019-06-12-29/+30
| |/ |/| | | | | | | - Keep .wake as an alias until we're certain it can be removed. - Enable SAB memory
* | 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
| * 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
| |