summaryrefslogtreecommitdiff
path: root/js
Commit message (Collapse)AuthorAge
* Issue #1805 - Follow-up: Include the same headers for Solaris as well to1805-stacksizeMoonchild2022-07-15
| | | | future-proof gcc versions.
* Issue #1805 - Follow-up: provide for Linux builds using rlimit and min/max.Moonchild2022-07-15
|
* Issue #1805 - Improve stack size limits for all targets.Moonchild2022-07-15
| | | | | | | | | | | | | This allows us to use a greater rendering depth for exceedingly-deep DOM trees in layout, better matching what mainstream browsers are capable of. Note that for 32-bit Windows the stack size MUST be set to larger than the default or Bad Things Will Happen™ - we use 1.5 MB for this as a carefully-tuned value. This needs to be capped specifically for JS use because some JavaScript obfuscators deliberately trigger stack overflows and would lock up the browser otherwise as long as there's still stack space to abuse. For web compatibility we therefore limit this to 2MB in JS only (3x for ASAN) while still allowing a greater depth for the layout engine.
* Issue #1952 - m-c 1440468: Proxied functions can't be passed to ↵Martok2022-07-01
| | | | Function.prototype.toString.call()
* Issue #1952 - m-c 1383775: Clean up function toString/toSource code, remove ↵Martok2022-07-01
| | | | remnants of source decompiler
* Issue #1952 - m-c 1380962/2: Remove unnecessary lambda function in ↵Martok2022-07-01
| | | | FunctionToString
* Issue #1952 - m-c 1380962/1: Merge append calls when assembling the source ↵Martok2022-07-01
| | | | string for native functions
* Issue #1952 - m-c 1371593: Avoid repeated string atomizations when ↵Martok2022-07-01
| | | | retrieving the unresolved name of a bound function
* Issue #1952 - m-c 1365387: Optimize FinishBoundFunctionInit by delaying ↵Martok2022-07-01
| | | | atomizing the function name
* Merge pull request 'Collected ports for async functions in the JS parser' ↵Moonchild2022-06-21
|\ | | | | | | | | | | (#1924) from martok/UXP-contrib:1918-asyncgenerator into master Reviewed-on: https://repo.palemoon.org/MoonchildProductions/UXP/pulls/1924
| * Issue #1918 - m-c 1353693: Correct parsing of async generator methodsMartok2022-06-17
| |
| * Issue #1918 - m-c 1353690: Properly exclude |await| from consideration as a ↵Martok2022-06-17
| | | | | | | | |let| variable name in async functions, so that a newline between the two separates them into two distinct expressions.
| * Issue #1918 - m-c 1345960: Handle shorthand property and destructuring with ↵Martok2022-06-17
| | | | | | | | | | | | async keyword properly. This was previously partially present, but got lost along the way
| * Issue #1918 - m-c 1358246: Report syntax error for stray "async" keyword in ↵Martok2022-06-17
| | | | | | | | object literal property name.
* | Issue #1905 - Part 4b - Fix issue loading the profile and saving changes to ↵Brian Smith2022-06-15
|/ | | | | | the profile. Based on the following Mozilla bugs: 1659904, 1659905 and 1659077.
* Issue #1905 - Part 3h - Fix breakages on other platforms.Brian Smith2022-06-10
| | | | | Mac Intel broke due to incorrect FFI target_dir for Intel. Linux and possibly other platforms use a secondary aclocal.m4 that still referenced ios.m4.
* Issue #1905 - Part 3g - Final set of changes connecting ARM64 support for Mac.Brian Smith2022-06-09
| | | | Back out some of the xptcstubs changes that are not viable for our codebase.
* Issue #1742 - Part 5: Remove unnecessary GCPtr::unbarrieredGetJeremy Andrews2022-05-27
| | | | Ref: BZ 1323441
* Issue #1742 - Part 4: Don't trigger read barriers when comparing wrapped ↵Jeremy Andrews2022-05-27
| | | | | | | | | pointers types This is actually an undocumented dependency of Bug 1325406 for Linux and SunOS. Ref: BZ 1308236
* Issue #1742 - Remove the ambiguous portions of gc that dealt with taggedMoonchild2022-05-25
| | | | | | | pointers for shapes. Nobody likes "isNullLike(obj)" when trying to garbage collect. It either is or is not. Master Yoda would be pleased with this change.
* Issue #1742 - Part 3: use JS::PropertyResult instead of Shape*Moonchild2022-05-24
| | | | | This is the meat of the issue and switches using raw shape pointers out for PropertyResult objects where feasible.
* Issue #1742 - Part 2: Add a class to encapsulate the possible results of a ↵Moonchild2022-05-24
| | | | property lookup
* Issue #1742 - Part 1: Refactor rooting base class templatesMoonchild2022-05-24
| | | | Based on Bug 1325406
* Issue #1894 - Part 7: Update testsFranklinDM2022-05-21
| | | | Based on https://bugzilla.mozilla.org/show_bug.cgi?id=1566141
* Issue #1894 - Part 6: Check for nullish values when folding coalesce nodesFranklinDM2022-05-21
| | | | | | | | This uses a different approach by modifying the `Boolish` function directly to act differently if we're checking for nullish values. Partially based on: Bug 1566141 - Implement the Nullish Coalescing operator (??) proposal Bug 1599163 - Nullish coalescing operator returns undefined for void expressions
* Issue #1894 - Part 5: Implement bytecode for nullish coalescingFranklinDM2022-05-21
| | | | Based on https://bugzilla.mozilla.org/show_bug.cgi?id=1566141
* Issue #1894 - Part 4: Implement IonMonkey support for nullish coalescingFranklinDM2022-05-21
| | | | Based on https://bugzilla.mozilla.org/show_bug.cgi?id=1566141
* Issue #1894 - Part 3: Implement support for nullish coalescing in JS reflectionFranklinDM2022-05-21
| | | | | | Partially based on: Bug 1566141 - Implement the Nullish Coalescing operator (??) proposal Bug 1593415 - Assertion failure: false, at js/src/builtin/ReflectParse.cpp:3092 with nullish coalescing
* Issue #1894 - Part 2: Implement support for nullish coalescing in the JS parserFranklinDM2022-05-21
| | | | Based on https://bugzilla.mozilla.org/show_bug.cgi?id=1566141
* Issue #1894 - Part 1: Implement coalesce JS opcodeFranklinDM2022-05-21
| | | | Based on https://bugzilla.mozilla.org/show_bug.cgi?id=1566141
* Issue #1658 - Part 8: Update testsFranklinDM2022-05-04
|
* Issue #1658 - Part 6: Break and return no control flow for jumps emitted by ↵FranklinDM2022-05-04
| | | | | | optional chains under IonBuilder IIUC, we want to process the GOTO in the case of optional chains, and we do not satisfy the requirements mentioned in the comment of snoopControlFlow's caller. Optional chains are not loops, we (probably) don't have a loop in the instruction following the GOTO, and in the GOTO destination, we're either returning an undefined/null value or the actual value.
* Issue #1658 - Part 5: Add and initialize TDZ check to optional chaining emitterFranklinDM2022-05-04
| | | | Partially based on: https://bugzilla.mozilla.org/show_bug.cgi?id=1685260
* Issue #1658 - Part 4: Fix optional chaining assertions and remove ↵FranklinDM2022-05-04
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | unreachable code This includes the following: Bug 1611777 - Part 1: Report syntax error for optional property access in self-hosting code. r=yulia! Bug 1611777 - Part 2: Merge same blocks in emitDeleteOptionalChain(). r=yulia! Bug 1611777 - Part 3: N/A Bug 1611777 - Part 4: `super` can't occur on the left-hand side of an optional chain Bug 1611777 - Part 5: Remove unnecessary super-handling in optional delete. r=yulia! The child node of a DeleteOptionalChainExpr node can't be a super-property accessor, so we can remove this code. Bug 1611777 - Part 6: Crash for unexpected super-base in optional call. r=yulia! Bug 1611777 - Part 7: Add missing entries to list of valid optional chain start expressions. r=yulia! Bug 1611777 - Part 8: Add missing emitGet in emitOptionalElemExpression. r=yulia! Aligns emitOptionalElemExpression() with emitOptionalDotExpression(), so it's easier to compare both methods against each other. Bug 1611777 - Part 9: Replace an if-statement with an assertion. r=yulia! Bug 1611777 - Part 10: N/A Bug 1611777 - Part 11: Support optional chaining in class heritage expression. r=yulia! Bug 1611777 - Part 12: Use optionalExpr() for update expressions to match spec grammar. r=yulia! Using optionalExpr matches the spec grammar more closely. This change also modifies the reported error message. ++a?.b reported before this change "unexpected token: '?.'", but now reports "invalid increment/decrement operand". Bug 1611777 - Part 13: N/A Bug 1611777 - Part 14: Simplify two lines in optionalExpr(). r=yulia! We don't need to test for tt == TokenKind::Eof when we return for tt != TokenKind::OptionalChain anyway. Omit local variable for the result value and instead use a tail-call. This matches the local style in the parser more closely. Bug 1611777 - Part 15: Support FunCall/FunApply optimisations for optional chaining. r=yulia! Bug 1611777 - Part 16: Pass through ValueUsage in optional chains. r=yulia
* Issue #1658 - Part 3: Implement support for optional chaining in JS reflectionFranklinDM2022-05-04
| | | | | | Partially based on: Bug 1610447 - Update Reflect to handle Optional Chaining operator Bug 1657835 - Assertion failure: false, at js/src/builtin/ReflectParse.cpp:3168
* Issue #1658 - Part 2: Implement bytecode for optional chainingFranklinDM2022-05-04
| | | | | | | Partially based on: Bug 1566143 - Implement the Optional Chaining operator (?.) proposal Bug 1650340 - Fix deleteElementInOptionalChain Bug 1644839 - Fix return value of emitOptionalChain on failure
* Issue #1658 - Part 1: Implement support for optional chaining in the JS ParserFranklinDM2022-05-04
| | | | Partially based on: https://bugzilla.mozilla.org/show_bug.cgi?id=1566143
* Merge branch 'master' into 1829Brian Smith2022-04-28
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * master: No issue - Update README and SECURITY Issue #1885 - Follow-up: Update error message if invalid rootMargin specified. Issue #1879 - Follow-up: Update config/external/nss/target to security/target. Issue #1885 - Allow unitless rootMargin entries for IntersectionObserver. Issue #1879 - Revert changes to cryptox.h Revert "Issue #1879 - spot-fix typo in cryptox.h" Issue #1879 - spot-fix typo in cryptox.h Issue #21 - Change MappedAttrParser to store its nsIPrincipal instead of nsSVGElement Issue #21 - Remove use counters telemetry Issue #1881 - Interpret empty or whitespace root margin string as zero length Issue #1877 - Resolve NIGHTLY_BUILD conditionals. Issue #1880 - Boot Comic Sans out of the font configuration.
| * Issue #1877 - Resolve NIGHTLY_BUILD conditionals.Moonchild2022-04-22
| |
* | Issue #1829 - Readd code cleanup that is not Mac related that got clobbered ↵Brian Smith2022-04-26
| | | | | | | | by reverting Issue #1751
* | Issue #1829 - Revert "Issue #1751 -- Remove XP_DARWIN"Brian Smith2022-04-26
| | | | | | | | This reverts commit 3d671e4275c73a1484c72713304c6e04ec4ffc7c.
* | Issue #1829 - Revert “Issue #1751 -- Remove XP_MACOSX conditionals from ↵Brian Smith2022-04-26
| | | | | | | | | | | | | | | | | | the rest of the tree.” This also removes some PP abuse and takes file entries out of PP when no longer needed without XP_MACOSX conditionals. This reverts commit 6f707bde95dab6998ac204f9ee6c925ee230c740.
* | Issue #1829 - Revert “Issue #1751 - Remove Mac code behind ↵Brian Smith2022-04-26
|/ | | | | | MOZ_WIDGET_TOOLKIT == 'cocoa’” This reverts commit 1fe9c19305dadf2d5bcaa0e589fcd250389dfa8a.
* Issue #1877 - Resolve RELEASE_OR_BETA conditionals.Moonchild2022-04-19
|
* Issue #1382 - Set canonical name for trimStart and trimEnd functionsFranklinDM2022-04-18
| | | | This is needed to fix the assertion on debug builds that self-hosted functions must have consistent names, as these two functions are aliased to `trimLeft` and `trimRight`.
* Merge pull request 'Issue #1818 Cleanup some old GCC hacks' (#1865) from ↵Moonchild2022-04-16
|\ | | | | | | | | | | trav90/UXP-contrib:compiler-hacks-cleanup into master Reviewed-on: https://repo.palemoon.org/MoonchildProductions/UXP/pulls/1865
| * Issue #1818 - Part 4: always use -pipe with GCCtrav902022-04-15
| | | | | | | | Usable GCC versions have supported -pipe for a VERY long time. There's no need to keep checking if it is supported.
| * Issue #1818 - Part 3: Remove more old gcc compiler hacks.trav902022-04-15
| |
| * Issue #1818 - Part 2: Remove code for implementation of atomics with __synctrav902022-04-15
| | | | | | | | | | All supported compilers support using C++11 <atomic> natively, so implementing this using GCC's old __sync functions is no longer necessary.
* | Issue #1864 - Fix IonBuilder::maybeMarkEmpty.Moonchild2022-04-15
|/ | | | | Look at the instruction's operands instead of the instruction itself, and take an early exit on empty types.
generated by cgit v1.2.3 (git 2.26.2) at 2024-11-10 02:35:37 +0000