We have a host of DEBUG-only dump()-style APIs that output either to
stderr or to a FILE*. Unfortunately, this means that we cannot use
these dumps e.g. for unit tests. This patch ports most of the dump()
APIs to use GenericPrinter, which is more flexible.
Some parts of the code have not been ported, in particular
TypeInference, which still uses stderr.
MozReview-Commit-ID: A5WGOPyIPTa
--HG--
extra : rebase_source : 2c092256569d7f0d5656acea9c6d7dbaf32667be
Seeing an NSVO in CreateObjectsForEnvironmentChain indicates the shared
global namespace is about to be polluted, so fix those bugs and turn
this to a diagnostic.
MozReview-Commit-ID: 7OUef76geJL
--HG--
extra : rebase_source : 07d826101a498c54faab5c99dc475818cad58c4b
When using the subscript loader with JSM global sharing, it was possible
that subscript would pollute the global of all JSMs in the sharing.
MozReview-Commit-ID: 1ah5JUAZwBA
--HG--
extra : rebase_source : 202904e30b582c788ec440c406607ba98b8836e6
We want to be able to store scripts compiled with or without
non-syntactic support in cache when we toggle JSM global sharing. In
current code this script is cloned on execution, but with JSM global
sharing we have would hit assertions.
MozReview-Commit-ID: 2pVTTxLpx6S
--HG--
extra : rebase_source : 5913a43a2dfddf74187f08ab9c53babe377bd706
This allows js::ExecuteInJSMEnvironment to take a target object argument
as used by the subscript loader. This adds WithEnvironments with a
corresponding lexical on top of the ordinary NonSyntacticVariablesObject
environment chain.
MozReview-Commit-ID: JhHEfV92Zpv
--HG--
extra : rebase_source : d1ef9564d30a25fd9e1cf1ca7e95bf40c780dcdf
Seeing an NSVO in CreateObjectsForEnvironmentChain indicates the shared
global namespace is about to be polluted, so fix those bugs and turn
this to a diagnostic.
MozReview-Commit-ID: 7OUef76geJL
--HG--
extra : rebase_source : b1cbf5d87622668c7a8ffaa413cada06a16f66fd
When using the subscript loader with JSM global sharing, it was possible
that subscript would pollute the global of all JSMs in the sharing.
MozReview-Commit-ID: 1ah5JUAZwBA
--HG--
extra : rebase_source : 45a3974cb80ede0cb3beea92f895679c5ea7aa4b
We want to be able to store scripts compiled with or without
non-syntactic support in cache when we toggle JSM global sharing. In
current code this script is cloned on execution, but with JSM global
sharing we have would hit assertions.
MozReview-Commit-ID: 2pVTTxLpx6S
--HG--
extra : rebase_source : b123de20f216161c408bba75c8c0fd81be0508df
This allows js::ExecuteInJSMEnvironment to take a target object argument
as used by the subscript loader. This adds WithEnvironments with a
corresponding lexical on top of the ordinary NonSyntacticVariablesObject
environment chain.
MozReview-Commit-ID: JhHEfV92Zpv
--HG--
extra : rebase_source : d1ef9564d30a25fd9e1cf1ca7e95bf40c780dcdf
The files relevant to the memory allocator are currently spread between
memory/mozjemalloc and memory/build, and the distinction was
historically from sharing some Mozilla-specific things between
mozjemalloc and jemalloc3. That distinction is not useful anymore, so
we fold everything together.
As we will likely rename the allocator at some point in the future, it
is preferable to move away from the mozjemalloc directory rather than in
its direction.
--HG--
rename : memory/mozjemalloc/Makefile.in => memory/build/Makefile.in
rename : memory/mozjemalloc/mozjemalloc.cpp => memory/build/mozjemalloc.cpp
rename : memory/mozjemalloc/mozjemalloc.h => memory/build/mozjemalloc.h
rename : memory/mozjemalloc/mozjemalloc_types.h => memory/build/mozjemalloc_types.h
rename : memory/mozjemalloc/rb.h => memory/build/rb.h
Seeing an NSVO in CreateObjectsForEnvironmentChain indicates the shared
global namespace is about to be polluted, so fix those bugs and turn
this to a diagnostic.
MozReview-Commit-ID: 7OUef76geJL
--HG--
extra : rebase_source : 487ab155a11e41d01b7195ac974b46e3bd2199b6
