- 26 8月, 2022 15 次提交
-
-
由 Michal Strehovský 提交于
This reverts commit 02c2ba0e.
-
由 Michal Strehovský 提交于
-
由 Aaron Robinson 提交于
* DisableRuntimeMarshalling block Vector types When DisableRuntimeMarshalling is set, the runtime should block a bad-list for blittable types. This doesn't address the case where the P/Invoke is inlined.
-
由 dotnet-maestro[bot] 提交于
* Update dependencies from https://github.com/dotnet/arcade build 20220823.2 Microsoft.DotNet.ApiCompat , Microsoft.DotNet.Arcade.Sdk , Microsoft.DotNet.Build.Tasks.Archives , Microsoft.DotNet.Build.Tasks.Feed , Microsoft.DotNet.Build.Tasks.Installers , Microsoft.DotNet.Build.Tasks.Packaging , Microsoft.DotNet.Build.Tasks.TargetFramework , Microsoft.DotNet.Build.Tasks.Templating , Microsoft.DotNet.Build.Tasks.Workloads , Microsoft.DotNet.CodeAnalysis , Microsoft.DotNet.GenAPI , Microsoft.DotNet.GenFacades , Microsoft.DotNet.Helix.Sdk , Microsoft.DotNet.PackageTesting , Microsoft.DotNet.RemoteExecutor , Microsoft.DotNet.SharedFramework.Sdk , Microsoft.DotNet.VersionTools.Tasks , Microsoft.DotNet.XUnitConsoleRunner , Microsoft.DotNet.XUnitExtensions From Version 7.0.0-beta.22419.1 -> To Version 7.0.0-beta.22423.2 * Update dependencies from https://github.com/dotnet/arcade build 20220824.3 Microsoft.DotNet.ApiCompat , Microsoft.DotNet.Arcade.Sdk , Microsoft.DotNet.Build.Tasks.Archives , Microsoft.DotNet.Build.Tasks.Feed , Microsoft.DotNet.Build.Tasks.Installers , Microsoft.DotNet.Build.Tasks.Packaging , Microsoft.DotNet.Build.Tasks.TargetFramework , Microsoft.DotNet.Build.Tasks.Templating , Microsoft.DotNet.Build.Tasks.Workloads , Microsoft.DotNet.CodeAnalysis , Microsoft.DotNet.GenAPI , Microsoft.DotNet.GenFacades , Microsoft.DotNet.Helix.Sdk , Microsoft.DotNet.PackageTesting , Microsoft.DotNet.RemoteExecutor , Microsoft.DotNet.SharedFramework.Sdk , Microsoft.DotNet.VersionTools.Tasks , Microsoft.DotNet.XUnitConsoleRunner , Microsoft.DotNet.XUnitExtensions From Version 7.0.0-beta.22419.1 -> To Version 7.0.0-beta.22424.3 Co-authored-by: Ndotnet-maestro[bot] <dotnet-maestro[bot]@users.noreply.github.com>
-
由 Ahmet İbrahim AKSOY 提交于
* Fix: Initial attempt to fix - ut passed * Update: Forgotten save * Update: Clear and Dispose ops on handles * Update: Activate tests for Unix and correct no reuse behavior * Update: Review Changes * Update: Deleted forgotten comment * Update: Review change
-
由 Jan Kotas 提交于
Document the recent engineering system improvements
-
由 Ankit Jain 提交于
* CI: Tighten the path based triggers for jobs `subsets`: - `mono`: exclude all `src/mono/wasm`, since any changes in that will trigger the wasm jobs anyway - `runtimetests`: exclude Wasm.Build.Tests, and Wasm.Debugger.Tests, both of which are in `src/tests/BuildWasmApps`, but are *not* related to runtime tests. - `coreclr_jit`: exclude `src/mono/*` completely, unrelated. Also, exclude `eng/pipelines/common/evaluate-default-paths.yml` from all the subsets, so changes in that doesn't trigger unncessary builds. * Address review feedback
-
由 Steve Molloy 提交于
* Re-enable MemoryCacheTest.Contains. Add a little more info in case of failures.
-
由 Aleksey Kliger (λgeek) 提交于
Partially reverts https://github.com/dotnet/runtime/pull/68991 When LLVM code calls non-LLVM code it will pass arguments in SIMD registers which the non-LLVM code doesn't expect Fixes https://github.com/dotnet/runtime/issues/73454 (issue 1)
-
由 Tomas Weinfurt 提交于
* update Helix arm64 images * update images * fix conditions * uopdate docker images * update containers * update debian containers * update ubuntu * update ubuntu
-
由 Aaron Robinson 提交于
* Reenable class-memaccess warning * Match x64 logic in emitarm.cpp * Make GCProtect sections with "gc" variable consistent Co-authored-by: NJan Kotas <jkotas@microsoft.com>
-
由 Radek Zikmund 提交于
* Disable ConnectWithRevocation_ServerCertWithoutContext_NoStapledOcsp on NativeAoT * Disable tests against #70981 instead
-
由 David Wrighton 提交于
An evaluation of the cost of "Copy native test components to test output folder" indicates that there are 2 major performance bottlenecks in that routine. There are the findings I had 1. The routine spends significant time loading every test project into msbuild to determine what to do. This processing takes as much as 400ms per test on hardware which has slow IO performance. 2. On Unix platforms, when producing the test script binaries, we make the scripts executable by using chmod. This ALSO takes as long as 400ms on the slowest platforms. 3. Actually copying the native binaries around is extremely cheap and fast, and the cost to generate the test scripts is also fairly low. This change addresses both of these issues. 1. For the issue that we look into each test project to determine what to do, I observed that for tests which are pri1 tests, when running a pri0 only job, we don't need to even examine any of the tests marked as exclusively pri1. This is a bit of a hack, but it does seem to work quite well. 2. For the chmod issue, since we don't actually maintain the executable bit when sent to helix, I set an msbuild property when generating the scripts during the "Copy native test components to test output folder" to just not set that flag. Results: Mac OSX test run jobs take ~8 minutes to run this portion of the build, down from ~27 minutes. Performance improvements are visible on all architectures/OS pairings, but they aren't as dramatic.
-
由 Filip Navara 提交于
Fixes tests on big endian platforms.
-
由 Tomas Weinfurt 提交于
-
- 25 8月, 2022 24 次提交
-
-
由 Shay Rojansky 提交于
To unblock CI build failures, works around #74170
-
由 Michal Strehovský 提交于
-
由 Ankit Jain 提交于
* [wasm] Move stable jobs from runtime-staging to runtime - library tests: windows - AOT tests: windows - Debugger tests (chrome): windows, and linux - Wasm.Build.Tests: windows * Move last remaining wasm-firefox tests to runtime too * Move firefox debugger tests to runtime-extra-platforms * Fix browser-eventpipe build ``` src/mono/sample/wasm/browser-eventpipe/Program.cs(80,13): error IDE0074: (NETCORE_ENGINEERING_TELEMETRY=Build) Use compound assignment ```
-
由 Alexander Köplinger 提交于
**BYPASS_SECRET_SCANNING**
-
由 Eric Erhardt 提交于
System.Runtime.Serialization.Schema isn't getting a NuGet package created for it because it doesn't set IsPackable=true.
-
由 Jan Kotas 提交于
This change was attempted before in https://github.com/dotnet/coreclr/pull/23029 and rejected due to performance impact. Things have changed since then that makes it feasible now. Sockets and file I/O do not use pinning feature of Overlapped anymore. They pin memory on their own using `{ReadOnly}Memory<T>.Pin` instead. It means that the async pinned handles are typically not pinning anything. The async pinned handles come with some extra overhead in this common use case. Also, they cause confusion during GC behavior drill downs. This change removes the support for async pinned handles from the GC: - It makes the current most common Overlapped use cheaper. It is hard to measure the impact of eliminating async pinned handles exactly since they are just a small part of the total GC costs. The unified fully managed implementation enabled simplificication of the implementation and reduced allocations. - It gets rid of confusing async pinned handles behavior. The change was actually motivated by a recent discussion with a customer who was surprised by the async pinned handles not pinning anything. They were not sure whether it is expected behavior or whether it is a bug in the diagnostic tools. Micro-benchmarks for pinning feature of Overlapped are going to regress with this change. The regression in a micro-benchmark that runs Overlapped.Pack/Unpack in a tight loop is about 20% for each pinned object. If there is 3rd party code still using the pinning feature of Overlapped, Overlapped.Pack/Unpack is expected to be a tiny part of the end-to-end async flow and the regression for end-to-end scenarios is expected to be in noise range.
-
由 Meri Khamoyan 提交于
* #50575 colorbehavior default should disable colors in android/applemobile
-
由 Michal Strehovský 提交于
* Only stack allocate when marshalling Utf8 arguments Fixes #74394. * Review feedback
-
由 Adam Sitnik 提交于
-
由 Jan Vorlicek 提交于
This change enables caching of the last used writeable mapping for W^X. It was originally disabled by an ifdef, but after we've turned W^X on by default, performance tests have shown a regression in some regex tests. I have investigated those and found that they do excessive amount of jitting (around 50000 methods). Enabling the caching of the last used writeable mapping fixes the regression completely. The caching implementation was present in the sources ever since I've implemented the W^X stuff, but if was disabled by an ifdef. So this change just defines the related symbol and enables the code. The caching basically just keeps a writeable mapping after unmapping until the next mapping request arrives, so it gives an opportunity to reuse it in case of series of mappings of sequential range of executable memory, which happens e.g. in the case mentioned.
-
由 Simon Rozsival 提交于
* WIP: add gRPC tests * Fix AOT and trimming * WIP * Implement IncludeNetworkSecurityConfig * Use IncludeNetworkSecurityConfig * Fix gRPC test * Avoid git checkout * Remove unnecessary code * WIP: start working on CI configuration * Remove WinHttpHandler * Fix problem with SSL * Change server host * Setup CI (#1) * Get Docker container building & exported via test build * Changes * Add missing pfx certificate * changes * cleanup Co-authored-by: NSimon Rozsival <simon@rozsival.com> * Use tls * Update yml * Revert changes to the mono Android sample app * Bump android image version * Bump image version * Enable TLS * Remove hardcoded package versions * Update package versions * Update package versions * Rename pipeline * Move interop tests website dependencies versions to Versions.props * Add cred scan supression for the interop test server private key * Fix licenses * Remove dependencies * Fix path to Versions.props * Remove unnecessary dependency version * Fix building docker image * Change pfx password Co-authored-by: NJo Shields <directhex@apebox.org>
-
由 Peter Sollich 提交于
Working with StressLogAnalyzer I found yet another issue where we are missing an initialization when re-running the analysis - when you add a format string to look for via the -f option, and then later remove it, it's not actually removed, but is still found. (#74491) missing an initialization when re-running the analysis - when you add a format string to look for via the -f option, and then later remove it, it's not actually removed, but is still found. The fix is simply to clear the s_interestingStringTable above the fixed entries.
-
由 Michal Strehovský 提交于
* If we're only building Pri-0 tests, don't try to AOT compile Pri-1 tests. `_WillCLRTestProjectBuild` is the property that checks for that. * Targeting pack references get injected in a way that the compiler targets don't see. The compiler targets are written for publish scenarios but we're not doing a publish. Fixes #68394
-
由 Steve Molloy 提交于
-
由 Anton Lapounov 提交于
-
由 Aaron Robinson 提交于
* Remove all non-functional/non-informational uses of mscorlib.
-
由 Ankit Jain 提交于
* [wasm] Use explicity allowed ports with playwright, on linux too Fixes https://github.com/dotnet/runtime/issues/72436 . * [wasm] Quote path, and arguments for wasm app host Fixes use of app host on windows, when it's installed in `c:\program files`. * Update BrowserRunner.cs
-
由 Aleksey Kliger (λgeek) 提交于
Due to rearranging the logic in #64102 we already inflated the interfaces that are generic instances. Inflating again is wrong and will use the wrong generic context. * use member access, not type punning * Add regression test for #70190 * Assert that overrides are already inflated how we expect * remove unused var * Remove one more inflate, there's nothing to do In https://github.com/dotnet/runtime/pull/64102#discussion_r790019545 we concluded that this branch is never taken. * Add link to issue for failing tests
-
由 Tanner Gooding 提交于
-
由 Pavel Savara 提交于
-
由 Tomáš Rylek 提交于
In my change adding support for default static virtual interface method implementations I made a subtle bug that caused behavioral change for some pre-existing constrained virtual calls that newly started to require runtime lookup. This is unnecessary and perf-negative, I have modified the code so that my change kicks in only for static virtual methods. Thanks Tomas
-
由 SingleAccretion 提交于
* Add a test * Allow SIMD-returning calls as arguments As of this change we handle all relevant ABI scenarios. 1) Windows x64: - SIMD8: returned and passed as "TYP_LONG", fine. - SIMD12 / SIMD16 / SIMD32: returned and passed via a return buffer, fine. 2) Unix x64: - SIMD8: returned and passed in one FP register, fine. - SIMD12 / SIMD16, Vector4: returned and passed in two FP registers, fine. - SIMD16, Vector128 / SIMD32: returned and passed via a return buffer, fine. 3) x86: - SIMD8: can be returned via two registers or a return buffer (and is always passed on stack), both are fine. - SIMD12/SIMD16/SIMD32: returned via a return buffer, passed on stack, fine. 4) ARM64: - SIMD8, Vector2: returned in two FP registers (and passed as such or "TYP_LONG" under Windows varargs), fine. - SIMD8, Vector64: returned in one FP register, can be passed as such or as "TYP_LONG" under Windows varargs. The latter case is now handled correctly in "Lowering::LowerArg". - SIMD12: returned in three FP registers, passed as such or in two integer registers under Windows varargs, fine. - SIMD16, Vector4: returned in four FP registers, passed as such, or in two integer registers under Windows varargs, fine. - SIMD16, Vector128: returned in one FP register, passed as such, or in two integer registers under Windows varargs, fine (morph will decompose the varargs case into a `FIELD_LIST` via a temp).
-
由 Jeremy Koritzinsky 提交于
-
由 DeepakRajendrakumaran 提交于
Details: Previously ISA flags were represented as bits in a 64 bit variable. This limited the total number of possible ISAs to 64. This change modifies this and starts using an array of 64 bit vars to store ISA flags. The main changes are in InstructionSetGenerator.cs. This drives a lot of other changes in this commit which are generated files.
-
- 24 8月, 2022 1 次提交
-
-
由 Jan Vorlicek 提交于
* Improve windows hardware exception handling performance With my recent change that modified hardware exception handling so that the related managed exception is thrown directly from the vectored exception handler, the performance of handling such exceptions have regressed. Several exception handling dotnet/performance microbenchmarks have regressed upto 15%. The reason for the regression was the larger number of stack frames between the exception raising and the actual handler frame. With a recent change that @AntonLapounov has made to fix process corrupting exceptions handling, the regression went down to 8%. This change moves the location where we raise the exception down to the ClrVectoredExceptionHandlerShim, which means to the closest possible frame to the managed code. This gets rid of the regression completely.
-