Comparing changes

Co-authored-by: JamesNK <JamesNK@users.noreply.github.com>

…3632. (#84960) * [LoongArch64] revert the modification about the LA64's PageSize by #83632. * keep the comment by CR.

The instructions were valid only for Xamarin projects which run linker during build. .NET Console projects only run linker during publish, so the instructions need to look different.

On my machine, depending on the order in which the tests end up running, the suite takes anywhere between 50 seconds and 130 seconds. With these changes, it's fairly consistently around 50 seconds. The majority of the time is spent in building new Regex instances with the source generator. This change just applies to a few of the test classes with _lots_ of test cases the same batching-in-the-source-generator approach we've taken in other test classes.

* Adding Vector128.GetElement. * Cases with 32b and smaller elements are now spill+load. * Addressed review comments. * Code cleanup.

* bump System.Text.Json timeout to 45 minutes * feedback

This is part of #84489 - landing support for async JS interop on threadpool threads in multi-threaded WebAssembly. Provides two pieces of functionality: 1. A keepalive token that can be used to prevent the current POSIX thread from terminating when it returns from its thread start function, or from an invocation from the JS event loop. When the last keepalive token is destroyed (assuming Emscripten isn't keeping the thread alive for other reasons) it will terminate as if by calling `pthread_exit` and the webworker will be made available to other threads 2. A `HasUnsettledInteropPromises` property that peeks `_js_owned_object_table` to see if there are any promises created by the interop subsystem that have not been fulfilled or rejected yet. * [mono] add internal WebWorkerEventLoop utility class Provides two pieces of functionality: 1. A keepalive token that can be used to prevent the current POSIX thread from terminating when it returns from its thread start function, or from an invocation from the JS event loop. When the last keepalive token is destroyed (assuming Emscripten isn't keeping the thread alive for other reasons) it will terminate as if by calling `pthread_exit` and the webworker will be made available to other threads 2. A `HasUnsettledInteropPromises` property that peeks `_js_owned_object_table` to see if there are any promises created by the interop subsystem that have not been fulfilled or rejected yet. * Use a per-thread unsettled promise count for mono_wasm_eventloop_has_unsettled_interop_promises we can't use the _js_owned_object_table size because it contains other interop objects, not just promises * remove old emscripten keepalive workaround hack * Add a more general getter for JS interop to keep a webworker alive And link to #85052 for more details * fixup docs

…ion (#85108)

* Accelerate Vector512 `ConvertToSingle` and `ConvertToInt32`. * Moving intrinsics to proper place.

* [wasm] Disable failing AOT test - System.Collections.Immutable Issue: #85012 * [wasm] Disable failing AOT tests - System.Runtime.Serialization.Xml* - System.Runtime.Serialization.Xml.Tests - System.Runtime.Serialization.Xml.ReflectionOnly.Tests Issue: #85013

* Accelerate Vector512 multiply. * Accelerate Vector512 divide. * Small build fix. * Fix accidental removal for Vector256_op_division. * Review edits. * Assert fix. --------- Co-authored-by: Tanner Gooding <tagoo@outlook.com>

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Comparing changes

Open a pull request

Commits on Apr 20, 2023

This comparison is taking too long to generate.