- 11 6月, 2021 15 次提交
-
-
由 Viktor Hofer 提交于
* Don't reference ns.dll inside shared framework The netstandard.dll shim shouldn't be referenced inside the shared framework as it's a compat shim that shouldn't be required to compose the shared framework. This removes the necessity of a separate RefPath build and improves incremental build times as only the few OOB projects that require the shim would need to rebuild. * Reference netstandard shim in OOBs that require it There are a few OOB projects that require the netstandard.dll shim as they intentionally reference projects that only expose a netstandard configuration. Co-authored-by: NBuyaa Namnan <buyankhishig.namnan@microsoft.com>
-
由 John Salem 提交于
-
由 dotnet-maestro[bot] 提交于
[main] Update dependencies from mono/linker
-
由 Aaron Robinson 提交于
* Make the ZLib P/Invokes all blittable
-
由 Zoltan Varga 提交于
-
由 Stephen Toub 提交于
The only time {U}Int{32/64}.TryParse needs to consult a culture is if it needs to look up the negative symbol from it, and if NumberStyles.None or NumberStyles.HexNumber are passed, it won't ever do that. All such call sites benefit from using CultureInfo.InvariantCulture explicitly, as it's just a static field read, whereas passing in null causes the implementation to access CultureInfo.CurrentCulture, which incurs a thread-static read. Most of our usage already does this, but a few sites don't; this fixes those.
-
由 Sergey Andreenko 提交于
* Add a repro. * small ref of `VNApplySelectorsAssignTypeCoerce`. * Fix the bug. * fix comment * Update src/coreclr/jit/valuenum.cpp Co-authored-by: NAndy Ayers <andya@microsoft.com> * Update src/coreclr/jit/valuenum.cpp Co-authored-by: NAndy Ayers <andya@microsoft.com> Co-authored-by: NAndy Ayers <andya@microsoft.com>
-
由 Vadim Zhukov 提交于
* Fix Sysctl() in buffer size autodetection mode The code private static unsafe void Sysct() in the Interop/BSD/System.Native/Interop.Sysctl.cs has two flaws in the case value == null && len == 0. First, in case of failure, this code doesn't call FreeHGlobal() on the memory it allocated right before. I.e., we have pure memory leak. Second, the "I don't know how much memory is needed, please allocated it by yourself" idea standing behind value == null && len == 0 assumes the Sysctl() itself being responsible to avoid ENOMEM condition. It could happen when, for example, we ask to list all processes in the system: this list could be expanded between first and second actual sysctl() calls, making the second call fail. So instead of a single try, we should try to allocate a bit more memory and try again; not force all our callers to do this themselves, by catching InvalidOperationException and analyzing it. Fixes #52823 * add missing IntPtr <-> int casts
-
由 Pavel Savara 提交于
avoid using crypto in WASM unit tests so that we could cover more scenarios
-
由 Michal Strehovský 提交于
Unless I'm missing something, this is equivalent. The previous version was incomprehensible to static analysis.
-
由 Michal Strehovský 提交于
Assembly.Location is an empty string when published as a single file.
-
由 Manish Godse 提交于
-
由 Steve Harter 提交于
-
由 Peter Sollich 提交于
Test GC\Scenarios\Boxing\variantlinklist\variantlinklist encountered a mark stack overflow that we didn't handle correctly in the regions case. The problem was that this was a gen 2 GC, and we didn't iterate over the gen 0 and gen 1 regions, so the objects causing the mark stack overflow were in fact not revisited. The fix is to iterate starting from gen 0 rather than the condemned generation. I added an assert to make sure process_mark_overflow_internal has found at least one marked object to process - unfortunately, we can check this only for WKS GC.
-
由 Peter Sollich 提交于
There are several tests (most of them under GC\Scenarios\DoublinkList) that fail because STRESS_REGIONS pins arbitrary objects and thus keeps them alive, and thus these objects are not finalized. Let's disable STRESS_REGIONS in the checked-in source code, but investigate whether there are any failures with STRESS_REGIONS that are real issues.
-
- 10 6月, 2021 25 次提交
-
-
由 Hugo Woodiwiss 提交于
* Set SupportedOSPlatforms at assembly level Update build props to set SupportedOSPlatforms to windows assembly wide
-
由 Tomas Weinfurt 提交于
* keep MsQuicConnection alive when streams are pending * remove extra file * fix gchandle * feedback from review * feedback from review * feedback from review
-
由 Alexander Köplinger 提交于
It seems to hang for some reason. https://github.com/dotnet/runtime/issues/53987
-
由 Fan Yang 提交于
-
由 Jan Vorlicek 提交于
* Add writeable holders for executable memory This change adds holders for writeable mappings for executable memory. It is the largest part of the W^X support. The ExecutableWriterHolder implementation is dummy in this change, but it was fully tested with coreclr / libraries tests on Windows arm, arm64, x64 and x86 with the real double memory mapping. There are few concepts / conventions used: * When the writeable pointer isn't known at a place where it is needed and also not at the caller, the ExecutableWriterHolder instance is created. * When a callee needs writeable pointer to executable memory and caller knows RW and RX, the argument is doubled with RX and RW suffixes. For constructors and member methods when "this" is the RW one, we pass just extra RX argument. * Locals holding RW pointer use RW suffix. * Locals holding RX pointer usually have no suffix to minimize number of changes, but in some cases they have a RX suffix where I felt like it was better to make things clear.
-
由 Maryam Ariyan 提交于
-
由 Alexander Köplinger 提交于
We were returning true even though sockets don't work on Browser. Co-authored-by: NMarie Píchová <11718369+ManickaP@users.noreply.github.com>
-
由 Johan Lorensson 提交于
-
由 Radek Doulik 提交于
Fixes: https://github.com/dotnet/runtime/issues/52008 When running `Microsoft.Extensions.Http` tests on windows and targeting `Browser`, the line ending differs between host and target systems. Use helper `LineEndingsHelper.Normalize` method to update expected strings. The `Browser` Environment.NewLine is `\n`, while windows use `\r\n`. https://github.com/dotnet/runtime/blob/5bd0edfe860e41bdfd690d3743e730594307292e/src/libraries/System.Private.CoreLib/src/System/Environment.UnixOrBrowser.cs#L51
-
由 Adam Sitnik 提交于
-
由 Stephen Toub 提交于
This was accidentally removed as part of a previous refactoring. The lack of it means primarily that we're not always removing async method tasks from the s_currentActiveTasks dictionary when the debugger is attached (we didn't notice it because awaiting the resulting task also causes it to be removed). It also means we're not clearing out some state we intended to in order to minimize extending lifetime of objects referenced by the state machine if the task is held onto for a prolonged period.
-
由 Lakshan Fernando 提交于
* Fix for Trim HW * FB
-
由 Viktor Hofer 提交于
See discussion here: https://github.com/dotnet/runtime/pull/53294#discussion_r648815525. That block isn't necessary anymore for source build.
-
由 ezgambac 提交于
fixes #53761
-
由 Emmanuel André 提交于
-
由 Jo Shields 提交于
* Use target OS strip tool, not host OS strip tool. Fixes Android on Mac build. * Try running objcopy when targeting Android, so we don't override it to "objcopy"
-
由 Kunal Pathak 提交于
* Remove crossgen SPMI collection * Remove reference of crossgen from superpmi.py * some misc crossgen references * put back deleted things
-
由 Drew Scoggins 提交于
-
由 Steve MacLean 提交于
-
由 Gleb Balykov 提交于
* Fix gcc armel build Mostly signed/unsigned comparisons, etc. * Fix gcc arm64 build
-
由 Steve MacLean 提交于
* Apple Silicon reenable 49110 failures * Restore test disables System.Numerics.Vectors & System.Runtime both failed for both runs. Restore disables of these tests.
-
由 Stephen Toub 提交于
-
由 Sergey Andreenko 提交于
-
由 Geoff Kizer 提交于
* remove StoreLocation and AddValue * make info.ParsedValue etc fields Co-authored-by: NGeoffrey Kizer <geoffrek@windows.microsoft.com>
-
由 Zoltan Varga 提交于
-