nsRect's special member functions are pretty vanilla aside from the MOZ_COUNT_{C,D}TORs, so the copy assignment doesn't need to do anything unusual, but let's state so explicitly to please the compiler.
Differential Revision: https://phabricator.services.mozilla.com/D60991
--HG--
extra : moz-landing-system : lando
When we set a thread to directory root, `item.path`, which is equal to `thread.actor` in a thread's case, is used as the project directory root and stored in `prefs`. When debugger is closed and reopened, `thread.actor` will be different. But the debugger state is initialized with an old directory root. For example, directory root is `server0.conn0.child1/thread19` from the last time, but thread is now "server0.conn1.child1/thread19."
I think it's error-prone to bump up `connX` by 1 when we see a `thread.actor` as `prefs.projectDirectoryRoot`. This patch removes the storage for threadActors, meaning when we set a thread to root, we don't keep track of it in `prefs`. Then we reopen the debugger, it doesn't show a thread as root. For other directories, `prefs` still works.
{F1862523}
Differential Revision: https://phabricator.services.mozilla.com/D58064
--HG--
extra : moz-landing-system : lando
We go to some lengths to defer FrameLoader initialization to the end of
document updates. However, it is still possible for initialization to happen
earlier as a side-effect of other operations (such as
`nsFrameLoader::GetBrowsingContext()`) if they're called before initialization
has already happened. Since this is such an easy mistake to make, we should
assert that it doesn't happen so that we find out about it sooner rather than
later.
Differential Revision: https://phabricator.services.mozilla.com/D55877
--HG--
extra : moz-landing-system : lando
We go to great lengths to try to avoid initializing FrameLoaders during
document updates. That means that when `BindToTree` is called, the element's
FrameLoader is not initialized, and it has no BrowsingContext. Calling
`GetBrowsingContext()` (which happens as a side-effect of
`HTMLIFrameElement::RefreshFeaturePolicy`), however, forces eager
initialization, which can cause any number of problems.
This patch moves that logic from being triggered by `BindToTree` to being
triggered by `BrowsingContext::Embed`, which happens as soon as the
BrowsingContext is bound to the element, but does not force it to be created
early.
Differential Revision: https://phabricator.services.mozilla.com/D55872
--HG--
extra : moz-landing-system : lando
Cranelift fails this assertion and it's not clear to me that there is any restriction inside
Cranelift that would limit the set of registers we'd need to check here.
Differential Revision: https://phabricator.services.mozilla.com/D58887
--HG--
extra : moz-landing-system : lando
This commit adds support for receiving stackmaps from Cranelift
and converting to wasm::Stackmaps. [1] will change the stackmap
representation in Cranelift to be the same as in Spidermonkey.
The stack overflow/interrupt trap handler stackmap is implemented by
sharing code with Ion.
[1] https://github.com/bytecodealliance/cranelift/pull/1317
Differential Revision: https://phabricator.services.mozilla.com/D58886
--HG--
extra : moz-landing-system : lando
cranelift-wasm cannot express arbitrary control flow inside of
'global.get/set' easily. This makes it difficult to implement the pre/post write
barriers inline like the baseline compiler does.
[1] has a discussion about the ideal solution to problem, which involves a new IR
concept called templates. We will want to use that when it is ready.
In the short-term, this commit implements pre/post write barriers using slow OOL
functions and implements Wasm globals.
[1] https://github.com/bytecodealliance/cranelift/issues/1176
Differential Revision: https://phabricator.services.mozilla.com/D58885
--HG--
extra : moz-landing-system : lando
This commit translates the basic parts of reference types that does not
require any barriers. AnyRef,FuncRef,NullRef are translated to R32/R64. The
existing bulk-memory instructions are extended to operate on multiple tables,
and the new reference type instructions are implemented with instance calls.
Differential Revision: https://phabricator.services.mozilla.com/D58884
--HG--
extra : moz-landing-system : lando
This commit changes the wasm compiler feature detection bits to report that
cranelift supports reference types.
Differential Revision: https://phabricator.services.mozilla.com/D58883
--HG--
extra : moz-landing-system : lando
Blocking here causes a problem on startup with the socket server, and
apps don't do this anyway.
Differential Revision: https://phabricator.services.mozilla.com/D60973
--HG--
extra : moz-landing-system : lando
Adds support for bind groups and compute pipelines
The end goal of this PR is to run the compute example.
Differential Revision: https://phabricator.services.mozilla.com/D60746
--HG--
extra : moz-landing-system : lando
This also adds an explicit warning when this happens so that the child processes don't crash without leaving a trace.
Differential Revision: https://phabricator.services.mozilla.com/D60650
--HG--
extra : moz-landing-system : lando
Avoid intermittent task timeouts by increasing wdspec test chunks from 2 to 3.
Differential Revision: https://phabricator.services.mozilla.com/D60963
--HG--
extra : moz-landing-system : lando
