summaryrefslogtreecommitdiffstats
path: root/js/public
Commit message (Collapse)AuthorAgeLines
* Issue #316 - Make the memory GC performance object conditional (WIP)wolfbeast2020-04-14-0/+2
| | | | | This was only added for GCubench and likely interfering with building without devtools-server.
* Simplify value setting.wolfbeast2020-01-09-66/+39
| | | | | This gets rid of unused boolean return values on setters and a level of indirection for calls to set values.
* Bug 1331092 - Part 7: Implement Async Generator yield*.Gaming4JC2019-12-17-1/+1
| | | | Tag #1287
* Bug 1331092 - Part 2: Implement Async Generator except yield*.Gaming4JC2019-12-17-1/+1
| | | | Tag #1287
* Issue #1302 - Add self-hosted implementation for string regex .matchAllwolfbeast2019-11-26-1/+1
| | | | This resolves #1302.
* Issue #1257 - Part1: Remove watch class-hook and proxy trap.wolfbeast2019-10-26-18/+2
|
* 1344477 - Part 1: Add JSOP_CALL_IGNORES_RV for function call that ignores ↵Gaming4JC2019-07-18-5/+17
| | | | return value.
* Remove AIX 1st party code OS checks, part 1wolfbeast2019-03-31-10/+0
| | | | Issue #186
* Force expected crashes on unexpected magic values.Nicolas B. Pierron2019-03-21-2/+5
|
* Remove telemetry leftovers from JS engine.adeshkp2019-01-30-8/+0
|
* Call memset on a void*, not a T*, in js_delete_poison to avoid ↵trav902018-09-12-1/+1
| | | | memset-on-nontrivial warnings with gcc that don't matter for an object whose lifetime is about to end
* Stop using PodZero in several places to initialize values of non-trivial typetrav902018-09-12-16/+7
|
* Avoid using memset on a not-trivial type like ServoSizestrav902018-08-18-1/+9
|
* Avoid using memset on a not-trivial type like TabSizestrav902018-08-18-1/+7
|
* Avoid doing a memset on a non-POD structuretrav902018-08-18-13/+33
| | | | | | |entryCount| tracks -- in fast-to-check manner -- the number of entries in the hashtable. But to actually enumerate entries, we have to loop through all of |table|, checking for entries that are actually live. A live entry is indicated by a zero |hash| in the entry. The |memset| would properly zero that; removing the memset will not. It's not entirely clear whether a memset that overwrites a lot of stuff but is maybe simpler, is faster than compiler-generated likely-SIMD code that zeroes out *just* |hash| fields in all the entries. But I am going to guess that SIMD is good enough. For now, we should just do the simple and thing: don't distinguish POD and non-POD, and know that the compiler is going to recognize that |mem.addr()->~T()| is a no-op when T is trivial. So with POD, the loop should degenerate to just zeroing |hash| at consistent offset, and SIMD will eat that up, and it can't be *that* different from the memset in performance (if it is at all).
* Refactor structured clone JSAPI to prevent mismatched scopes.wolfbeast2018-06-07-31/+176
| | | | Roll-up of bugs 1442722, 1455071, 1433642, 1456604 and 1458320.
* Bug 1411415.wolfbeast2018-04-29-4/+51
|
* Merge branch 'html_input_datetime_1'wolfbeast2018-04-15-0/+8
|\ | | | | | | This is almost everything needed for #162.
| * Bug 1310078 - Implement valueAsNumber and valueAsDate for <input ↵janekptacijarabaci2018-03-30-0/+8
| | | | | | | | type=datetime-local>
* | Fix Value::isGCThing footgun, stop returning true for NullValuetrav902018-04-07-42/+26
|/
* Add m-esr52 at 52.6.0Matt A. Tobin2018-02-02-0/+17568