- 30 6月, 2021 13 次提交
-
-
由 Eric StJohn 提交于
* Remove some redundant / unused binplace directories * Fix runtime pack path * Use OuputRid instead of PackageRID On linux-musl, OutputRID differs from PackageRID. * Add RuntimeOS to installer leg for musl So that we have consistent values of $(PackageRID) for installer and libraries * Move LibrariesConfiguration definition earlier in src/tests This property was being defined after a number of places where it was consumed resulting in quite a few inconsistent derived properties.
-
由 Pavel Savara 提交于
- browser http response stream could be seekable - test WebAssemblyEnableStreamingResponse
-
由 xtqqczze 提交于
-
由 Kunal Pathak 提交于
-
由 Ulrich Weigand 提交于
The recently added DoubleTests.cs:ParsePatterns test case incorrectly swaps characters of the hexadecimal representation of the floating-point numbers under test on big-endian platforms.
-
由 Viktor Hofer 提交于
* Use property to indicate NetCoreApp min version * Add NetCoreAppCurrent to S.Numerics.Tensors * Add NetCoreAppCurrent to S.T.AccessControl * Add NetCoreAppCurrent to System.Memory.Data * Add NetCoreAppCurrent to S.Composition.* projects * Add NetCoreAppCurrent to System.IO.Packaging * Add NetCoreAppCurrent config to System.IO.Ports Adding a NetCoreAppCurrent configuration to System.IO.Ports and reducing package size, build times and platform specific assets by using runtime checks on Unix derivates for the slightly diverging SerialPort implementation. Contributes to https://github.com/dotnet/runtime/issues/54012 * Add NetCoreAppCurrent to System.Data.OleDb * Add NetCoreAppCurrent to M.W32.Registry.AccessControl * Add NetCoreAppCurrent to S.Reflection.Context * Add NetCoreAppCurrent to S.C.Composition.Registration * Add NetCoreAppCurrent to S.Resources.Extensions * Add NetCoreAppCurrent to S.N.H.WinHttpHandler
-
由 Tal Aloni 提交于
* Sgen: Update progress when importing types * Null check * Remove trailing whitespace * Updated Strings.resx * Sgen: Use string resource
-
由 Alexander Nikolaev 提交于
A race condition between sending RST_STREAM and checking conditions for sending EndStream was discovered during stress testing. It happens to be possible that in time after Http2Stream [checked the _responseCompletionState](https://github.com/dotnet/runtime/blob/183c4d100f68fb6c177a1fe71809d581aa25e47b/src/libraries/System.Net.Http/src/System/Net/Http/SocketsHttpHandler/Http2Stream.cs#L275) and [actually send EndStream](https://github.com/dotnet/runtime/blob/183c4d100f68fb6c177a1fe71809d581aa25e47b/src/libraries/System.Net.Http/src/System/Net/Http/SocketsHttpHandler/Http2Stream.cs#L288), a concurrent call to [Cancel method sends a RST_STREAM frame](https://github.com/dotnet/runtime/blob/183c4d100f68fb6c177a1fe71809d581aa25e47b/src/libraries/System.Net.Http/src/System/Net/Http/SocketsHttpHandler/Http2Stream.cs#L389). Such reordering is disallowed by HTTP/2 protocol. Note: The issue and fix were verified manually under the debugger because currently it's not clear how to reliably simulate that situation. Fixes #42200
-
由 Geoff Kizer 提交于
* disable ConnectTimeout_TimesOutSSLAuth_Throws for HTTP3 * disable HTTP3 cookie tests Co-authored-by: NGeoffrey Kizer <geoffrek@windows.microsoft.com>
-
由 SingleAccretion 提交于
* Remove GTF_UNSIGNED check from the condition It is not necessary: GTF_UNSIGNED does not have anything to do with the operands being unsigned. Some positive diffs in runtime tests for win-x86 and one regression in System.Net.WebSockets.ManagedWebSocket.ApplyMask. The regressions is because we generate two "div"s for a long UMOD on x86 with a constant divisor, always, even for powers of two. Something to improve for sure. Naturally, no diffs for win-x64, linux-x64 or linux-arm. * Don't fold casts from constants in UMOD morphing It used to be that "ldc.i4.1 conv.i8" sequences survived importation, and since UMOD morphing is sensitive to constant divisors, morph tried to fold them. This is no longer the case, so stop doing that. Of course, morph can be called from anywhere at any point, but if some code is creating casts from constants, the proper place to fix is that code. No diffs for win-x86 or win-x64 or linux-arm. * Some code modernization Use modern helpers and move comments around.
-
由 David Wrighton 提交于
Handle marker types with more than 1 generic argument correctly when they must be materialized into full types (#54875)
-
由 Viktor Hofer 提交于
This reverts commit 8103a7e3.
-
由 dotnet-maestro[bot] 提交于
[main] Update dependencies from 11 repositories - Address new IL3002 and IL3003 warnings for the latest linker to unblock the build. - Disable the trim analyzer for tests with EnableAggressiveTrimming - Merge branch 'main' into darc-main-997daf91-1bd1-4e82-9eac-1347a9231dc5
-
- 29 6月, 2021 24 次提交
-
-
由 Zoltan Varga 提交于
-
由 Aleksey Kliger (λgeek) 提交于
-
由 imhameed 提交于
-
由 Tom Deseyn 提交于
-
由 Anton Firszov 提交于
-
由 Stephen Toub 提交于
-
由 Alexander Nikolaev 提交于
Enable Http2_MultipleConnectionsEnabled_InfiniteRequestsCompletelyBlockOneConnection_RemaningRequestsAreHandledByNewConnection test (#54683) Fixes #45204
-
由 Peter Sollich 提交于
Found a race condition where the LOH flag on a segment is set too late. This gives another thread the chance to allocate in a fresh LOH region that doesn't have the LOH flag set just yet and trip over an assert in Object::ValidateInner. (#54839) The fix is simply to set the flag in get_new_region before the region is put on the list for the LOH generation.
-
由 Peter Sollich 提交于
StressLogAnalyzer didn't print the number of messages correctly if it exceeded the int range (2 billion). (#54832) Fix is to just use 64 bit ints instead.
-
由 Tomas Weinfurt 提交于
-
由 Sergey Andreenko 提交于
-
由 Sergey Andreenko 提交于
* Add repro. * fix the issue. * delete a dead condition * add a todo. * Fix the failures.
-
由 Juan Hoyos 提交于
-
由 Aaron Kunkle 提交于
-
由 David Wrighton 提交于
Change interface map layout in two interesting ways 1. For interface maps defined in System.Private.CoreLib, rely on the C# compiler to prevent any ambiguous duplicates, and to find the full interface expansion, instead of expanding it within the type loader See code marked with #SpecialCorelibInterfaceExpansionAlgorithm - Note that this optimization is only applied for ValueTypes as the presence of inheritance makes the optimization much more complex in many cases, and isn't needed. - This optimization reduces the amount of parsing of the interface implementation table must be done for valuetypes in CoreLib. In particular, with the new interfaces that are added as part of #54650 there is a very deep interface hierarchy that requires a great deal of scanning. As those interfaces are added to all the primitive types, the impact on startup performance is significant and measurable. 2. For interface map expansion that follows the curiously recurring generic pattern, place the open instantiation of the type in the interface map instead of the the exact instantiation, and update all places in the runtime which consider the interface map to deal with that change (Mostly by adding special purpose logic to work with the special marker type in the interface map, but there is also logic to simply force the exact interface type to be loaded, when working with the partially loaded type is not quite good enough, or excessively complex) - This optimization reduces the set of interface types that need to be loaded if they are unused. Of particular benefit are the numerous interfaces associated with the primitive types that are added as part of #54650. Performance of launching an extremely simple .NET process (process with empty main method). Results acquired using local testing on my developer machine, using a simple script that launches the process 500 times in a row. | Before #54650 | After #54650 | After #54650 and #54588 (this pr) | | :-: | :-: | :-: | | 14.1ms | 16.5ms |14.3ms |
-
由 Jeremy Koritzinsky 提交于
* Use string constructor that takes length instead of the one that searches for a null terminator. Fixes #54662 * Marshal back buffer size or string to first null terminator, whichever is shorter * Add tests. * Add unicode test. * Use the same implementation style for the wstr case case as the cstr case * Fix accidental deletion from test.
-
由 Gleb Balykov 提交于
-
由 Larry Ewing 提交于
-
由 Larry Ewing 提交于
-
由 Larry Ewing 提交于
-
由 Wei Zheng 提交于
-
由 Kevin Jones 提交于
The two properties got different diagnostic IDs so that the messages could better reflect the caller recovery action.
-
由 Eric Erhardt 提交于
* First round of converting System.Drawing.Common to COMWrappers Using COM Wrappers makes the library trim compatible. * Add Trimming Test for Icon.Save * Add support for OS specific trimming tests * Use function pointers instead of delegates * Rename Guid to IID * Better interop to closely match the native side * Release any COM pointer that was QueryInterface * Use pointers instead of Marshal.PtrToStructure/StructureToPtr * No need for a VTable struct, just set each function pointer right into the table * Wrap all managed calls in try-catch and return HResult * Use COM naming * Fix method signature to use pointer instead of out. * CheckStatus => ThrowExceptionForHR * Pass -1 to Marshal.GetExceptionForHR so it doesn't query GetErrorInfo, and always returns the correct exception type * Create the PictureWrapper with UniqueInstance, so it doesn't get cached. Caching it causes lifetime issues.
-
由 Jeremy Koritzinsky 提交于
-
- 28 6月, 2021 3 次提交
-
-
由 Kevin Jones 提交于
This change adds SymmetricAlgorithm.EncryptEcb, SymmetricAlgorithm.DecryptEcb, their respective Try- and -Core methods, derived type implementations thereof, and tests. There's an open question of should these members on on the base class throw or "succeed if the Mode property is in agreement with the algorithm". While the latter is "nicer", just throwing is easier to reason about, and that's the current behavior. Co-authored-by: NJeremy Barton <jbarton@microsoft.com>
-
由 Maxim Lipnin 提交于
- added TargetFrameworkForNETCoreTasks property similar to NetCoreAppToolCurrent one as NetCoreAppToolCurrent will likely bump more aggressively between new sdks; - renamed TargetFrameworkForNETFramework to TargetFrameworkForNETFrameworkTasks.
-
由 Steve Pfister 提交于
The condition on the import group for the iOS and tvOS simulators was not valid since iOS/tvOSSimulator is not a `TargetPlatformIdentifier`. To simplify, the simulator imports were moved under iOS/tvOS. Fixes https://github.com/dotnet/runtime/issues/53427Co-authored-by: NSteve Pfister <steve.pfister@microsoft.com>
-