- 03 4月, 2022 6 次提交
-
-
由 dotnet-maestro[bot] 提交于
* Update dependencies from https://github.com/dotnet/linker build 20220330.1 Microsoft.NET.ILLink.Tasks From Version 7.0.100-1.22178.1 -> To Version 7.0.100-1.22180.1 * Update dependencies from https://github.com/dotnet/linker build 20220331.1 Microsoft.NET.ILLink.Tasks From Version 7.0.100-1.22178.1 -> To Version 7.0.100-1.22181.1 * Update dependencies from https://github.com/dotnet/linker build 20220401.3 Microsoft.NET.ILLink.Tasks From Version 7.0.100-1.22178.1 -> To Version 7.0.100-1.22201.3 Co-authored-by: Ndotnet-maestro[bot] <dotnet-maestro[bot]@users.noreply.github.com>
-
由 Bruce Forstall 提交于
Loop cloning needs to parse what morph creates from GT_INDEX nodes to determine if there are array accesses with bounds checks that could potentially be optimized. For jagged array access, this can be a "comma chain" of bounds checks and array element address expressions. For a case where an array of structs had a struct field, such as `ValueTuple<int[], int>[]`, cloning was confusing the expression `a[i].Item1[j]` for the jagged array access `a[i][j]`. The fix here is to keep track of the type of the `GT_INDEX` node that is being morphed, in the `GT_BOUNDS_CHECK` node that is created for it. (This is the only thing cloning parses, to avoid the need to parse the very complex trees morph can create.) This type is then checked when parsing the "comma chain" trees. If a non-`TYP_REF` is found (such as a `TYP_STRUCT` in the above example), no more levels of array indexing are considered. (`TYP_REF` is what an array object would have, for a jagged array.) Fixes #66254.
-
由 SingleAccretion 提交于
We can sometimes see trees like "ARR_ADDR(long 0)" that are the result of morph's folding logic. In general it does not seem great to allow folding of BYREFs into LONGs like that, but it is also not incorrect per-se.
-
由 Stephen Toub 提交于
* Add {ReadOnly}Span ctor (internal for now) that takes an in and no length * Address PR feedback * Fix native references to _pointer
-
由 madelson 提交于
Co-authored-by: NStephen Halter <halter73@gmail.com>
-
由 Wraith 提交于
* add quotes around dotnet path * address feedback
-
- 02 4月, 2022 30 次提交
-
-
由 Marie Píchová 提交于
-
由 dotnet bot 提交于
-
由 Eirik Tsarpalis 提交于
-
由 Michal Strehovský 提交于
Fixes #65612. This regression was exposed in #62891 - we had a mismatch between what methods are considered reflectable during scanning vs during optimized compilation due to extra array being injected for reflectable `params` methods on instantiated generic types. There are two potential fixes - either expand the set of methods considered reflectable during scanning, or limit the number of methods considered reflectable in optimized compilation. It doesn't look like we need the expanded set, so going with a restriction instead. The CI may prove me otherwise, so keeping an open mind about this.
-
由 Egor Bogatov 提交于
-
由 Tomáš Rylek 提交于
* Move copying of merged wrapper native components to copynative step * Move export of test exclusion file before ILLink changing CORE_ROOT * Fix file mode for test execution bash scripts * Add out-of-proc test folders to Helix work item payloads * Fix Helix publishing in the presence of out-of-process tests * Use a marker file triggered off of a project property to determine which files to skip running the Mono AOT compiler on (some tests fail at AOT time, so we need this to work around that limitation) * Pass runtimeVariant to the Core_Root construction for the test exclusion list creation * Don't write the output element when there's no test output. This causes issues with Helix test uploading. * Write xunit results the way xharness expects to read them for wasm so we correctly report failures and don't report a test harness failure. * Fix GeneratedTestRunner to build. * Fix copying native wrappers for merged test runners. Pre-emptively mark another test as RequiresProcessIsolation as I stumbled upon it while fixing this * Fix copying of native test components to merged wrapper outputs Due to Pri0 / Pri1 test grouping we may end up building the wrapper in a different group than its components. Make sure that we populate all native components of merged wrapper dependencies before we copy them over to the merged wrapper output folder. * Exclude wasm support files. Co-authored-by: NJeremy Koritzinsky <jekoritz@microsoft.com>
-
由 Mukund Raghav Sharma 提交于
Removed the hard heap limit heap balancing logic for regions + UOH and fixed infinite retries in case at the LOH boundary (#67406) * Removed the hard heap limit heap balancing logic for uoh and fixed inifite retries * Addressed feedback - refactored region checking directives * Removed all instances of hard_limit_exceeded_p as it is no longer needed
-
由 Bruce Forstall 提交于
Tracking: https://github.com/dotnet/runtime/issues/66921
-
由 Bruce Forstall 提交于
Tracking: https://github.com/dotnet/runtime/issues/58699
-
由 Bruce Forstall 提交于
Tracking: https://github.com/dotnet/runtime/issues/66279
-
由 Aaron Robinson 提交于
Remove `ObsoleteAttribute` from COM interop values.
-
由 judilsteve 提交于
* Detect systemd when inside a container. Modify IsSystemdService to function correctly for containerised services. Fix #67203 Adds conditional compilation to fall back to Process.GetCurrentProcess().Id when Environment.ProcessId is not available. * Apply suggestions from code review The minimum supported .NETCoreApp version in the repository is 6.0, so just using NETCOREAPP. Co-authored-by: james <judilsteve> Co-authored-by: NEric Erhardt <eric.erhardt@microsoft.com>
-
由 SingleAccretion 提交于
* Dissolve structs into primitives for PUTARG_STK The primary benefit of this change is "free" support for complex addressing modes, which is always desirable when we are loading a primitive (as opposed to the large struct case, where we would not want to use the 3-operand LEA in a loop, but instead cache the address in a register). The additional (future) benefit is that we will no longer need to mark the source local as DNER, once LCL_VAR sources for struct PUTARG_STKs are supported. * Contain PUTARG_STK sources for "push [mem]"
-
由 Tomáš Rylek 提交于
Today logic for emitting the legacy XUnit wrappers is based on scanning the test output tree for execution scripts (sh / cmd); we however need to emit execution scripts even in the presence of merged wrappers in case of tests requiring project isolation. This change filters these tests out so that they don't end up creating a spurious legacy XUnit test wrapper. Thanks Tomas
-
由 Jeremy Barton 提交于
Based on (non-exhaustive) testing, chain builds from a Let's Encrypt issued certificate have the following characteristics: * Live OCSP request required (uncached/unstapled): 577ms * OCSP response retrieved from cache (unstapled): 183ms * OCSP response utilized from TLS stapling (bypasses cache): 182ms In both cached and stapled the revocation portion was about 39ms. (The revocation mode was ExcludeRoot, the CRL pertaining to the intermediate was cached for all three measurements.) If the OCSP response was stapled (and the math worked out OK on it) then we completely ignore the OCSP cache. While it could potentially be useful to update the cache if the stapled response was newer, the extra I/O of doing the "newer" test didn't feel justified at this time.
-
由 github-actions[bot] 提交于
-
由 Anders Abel 提交于
This should improve the experience when working with complex SAML tokens.
-
由 Marie Píchová 提交于
* Update to msquic 2, test and code fixes * feedback * Fixed more HTTP/3 bugs * updated fedora image to contain the newest msquic * Better test debugging, fixed some timeouts * feedback * Return some msquic calls into a lock
-
由 Egor Bogatov 提交于
-
由 Maksym Koshovyi 提交于
-
由 Maksym Koshovyi 提交于
-
由 SingleAccretion 提交于
* Do not copy flags in ADDR/COMMA opt We only need to update the side effects, and gtUpdateNodeSideEffects already takes care of that. Will avoid copying GTF_NO_CSE unnecessarily. No diffs. * Add GT_ARR_ADDR * Generate ARR_ADDR in morph * gtSetEvalOrder tuning * Delete the ArrayInfo map * Delete GTF_IND_ARR_INDEX * Make ARR_ADDR non-null This preserves the non-faultness annotation for the parent indir when ADDR(IND(ARR_ADDR)) -> ARR_ADDR folding happends. * Simplify the array address parsing We don't need the field sequence or the complex parsing. A few diffs because previos code didn't handle COMMAs. (The new code doesn't either, but they are skipped automatically by the optComputeLoopSideEffectsOfBlock). * Clean ParseArrayAddress up Move it to GenTreeArrAddr, stop using ArrayInfo. * More ParseArrayAddress cleanup FldSeq no loger expected or needed. We will be attaching it to ARR_ADDR directly in the future. * Delete index labeling And associated code. No longer needed, and we will use a different mechanism for ARR_ADDR. No diffs. * Delete the last pseudo-field No longer needed... * Delete ArrayInfo * Fix formatting
-
由 Vlad Brezae 提交于
* [mono] Fix static virtual calls to generic methods from gshared code When the resolved method from the vtable is generic, we need to inflate it. For example, in the gshared method we are calling on `Interface.InterfaceMethod<int> ()` (the type argument can either be fixed or determined based on the gshared method's context), and this method is resolved to generic method `Class.InterfaceMethod<T> ()`. We then need to inflate the method and resolve `T` to `int`. * Enable tests * [mono][interp] Fix calls to static virtual methods via delegates * [mono][aot] Fix constrained + ldftn * [mono][gsharing] Fix constrained + ldftn from gshared method We can'd determine at compile time the static method if the constrained_class is a generic parameteri. We defer the computation of the method at runtime, in a similar fashion with calls. * Disable test suite on android It hits an issue in the android test runner
-
由 Carlos Sanchez 提交于
Co-authored-by: Ncarlossanlop <carlossanlop@users.noreply.github.com>
-
由 Larry Ewing 提交于
This reverts commit eaa1f05d.
-
由 Maksym Koshovyi 提交于
-
由 Andy Gocke 提交于
Publishes crossgen as an AOT binary on Windows+Linux x64+ARM64, otherwise publishes as an R2R single file. Closes #60016
-
由 Jeremy Koritzinsky 提交于
-
由 Tarek Mahmoud Sayed 提交于
-
https://github.com/dotnet/roslyn-analyzers由 dotnet-maestro[bot] 提交于
Microsoft.CodeAnalysis.NetAnalyzers From Version 7.0.0-preview1.22174.1 -> To Version 7.0.0-preview1.22180.6 Co-authored-by: Ndotnet-maestro[bot] <dotnet-maestro[bot]@users.noreply.github.com>
-
- 01 4月, 2022 4 次提交
-
-
由 Steve Pfister 提交于
Enabling because the underlying issues appear to have been fixed. https://github.com/dotnet/runtime/issues/56085 https://github.com/dotnet/runtime/issues/52460
-
由 Krzysztof Wicher 提交于
-
由 Eirik Tsarpalis 提交于
* Refactor metadata reading infrastructure. * Update src/libraries/System.Text.Json/src/System/Text/Json/Serialization/Converters/Object/ObjectConverter.cs
-
由 Jakob Botsch Nielsen 提交于
`ValueNumStore::GetVNFunc` is very hot, in fact so hot that it shows up right at the top in a profile of SPMI over libraries.pmi, next to `fgMorphSmpOp`. Instead of copying all args just return a pointer to the arguments which allows all the cases to be unified and makes the function small enough for MSVC to inline it. Most of the work here is to make sure we do not end up with undefined behavior. I also removed some of the duplication by using a templated struct for func apps instead of the old VNDefFuncNArg. Windows x64 SPMI over libraries.pmi: PIN before: 329991512865 PIN after: 326098430289 (-1.19%)
-