- 11 8月, 2023 21 次提交
-
-
由 Tanner Gooding 提交于
* Expose the RequiresLocationAttribute * Add a basic test for RequiresLocationAttribute
-
由 Eric StJohn 提交于
-
由 Tomas Weinfurt 提交于
* only slice SocketAddress on success operation * null * completed * feedback * feedback
-
由 JC 提交于
-
由 Steve Pfister 提交于
In https://github.com/dotnet/runtime/pull/89869, the call to the AppleAppBuilderTask passed an item for `NativeDependencies` as opposed to a property. The change wasn't reflected in the runtime test build.proj, so the built test app wasn't being sent in. Fixes https://github.com/dotnet/runtime/issues/90312 Fixes https://github.com/dotnet/runtime/issues/90218
-
由 Mitchell Hwang 提交于
-
由 Eric StJohn 提交于
-
由 Tarek Mahmoud Sayed 提交于
-
由 Fan Yang 提交于
* Add ILStrip task to wasm app build process * Make it work for wasm app building workflow * Interp: stop inlining stripped methods. ILStrip: set code size to zero for tiny methods * [mono][aot] Avoid adding some methods to the compiled method file. * Methods which have 'deopt' set can enter the interpreter during EH. * Methods which have 'interp_entry_only' set are AOTed, but the AOT code is only used to enter the interpreter. * Only trim the methods that interpreter is able to call the aot'ed verion of it * Add default value and documentation for WASMStripIL * Move jit_call_can_be_supported to interp.c * Minor format fix * Add a test * For testing * Fix typo * Skip TestUtilities Reference * Address review feedback * Change it to true * Change name to trimming eligible * Remove testing * Address review feedback * Address review feedback from Kate * Add a var for llvm_only --------- Co-authored-by: NZoltan Varga <vargaz@gmail.com>
-
由 Jeremy Koritzinsky 提交于
-
由 Mike Voorhees 提交于
This led to `[NoLinkedOutput]` being left in the `input` assembly
-
由 Jeremy Koritzinsky 提交于
Report a diagnostic for return types with HResult-like named structures and provide a code-fix to do the correct marshalling (#90282)
-
由 Egor Bogatov 提交于
-
由 Milos Kotlar 提交于
-
由 Alexander Köplinger 提交于
We have a separate pipeline for it and it is breaking official builds at the moment.
-
-
由 Zoltan Varga 提交于
[mono][llvm] Use the OP_MEMMOVE opcode instead of calling the managed memcpy method when compiling with LLVM. (#90097) LLVM can emit optimized code when the length ends up being a constant.
-
由 Miha Zupan 提交于
* Remove unsafe code and make scheme parsing faster in Uri * Reduce the number of range checks * Switch loop to IndexOf
-
由 Miha Zupan 提交于
-
由 Ivan Diaz Sanchez 提交于
Restored Crossgen2's optimizations in CoreCLR builds and reenabled the poisoning tests since the problem has been addressed. (#90278)
-
由 Jackson Schuster 提交于
[ComInterfaceGenerator] Add implementation and test for CallerAllocateBufferType parameters (#90263)
-
- 10 8月, 2023 19 次提交
-
-
由 Meri Khamoyan 提交于
-
由 Brennan 提交于
-
由 Viktor Hofer 提交于
The full RID graph is frozen and won't change anymore. Mark the Microsoft.NETCore.Platforms nuget package as non-shipping as only the sdk repository still requires it. Contributes to https://github.com/dotnet/runtime/issues/90000
-
由 Qiao Pengcheng 提交于
* [LoongArch64] Fix the `la.local` between the JIT_PatchedCodeStart and the JIT_PatchedCodeLast for the upstream's LA-compiler-bugs. * Also update the `g_GCShadowEnd`. * amend the code for CRs.
-
由 Pavel Savara 提交于
-
由 Steve Harter 提交于
-
https://github.com/dotnet/roslyn-analyzers由 dotnet-maestro[bot] 提交于
Microsoft.CodeAnalysis.Analyzers , Microsoft.CodeAnalysis.NetAnalyzers From Version 3.11.0-beta1.23405.1 -> To Version 3.11.0-beta1.23407.1 Co-authored-by: Ndotnet-maestro[bot] <dotnet-maestro[bot]@users.noreply.github.com>
-
由 Tomas Weinfurt 提交于
-
由 Jakob Botsch Nielsen 提交于
Physical promotion invokes `fgForwardSubStatement`, providing its own liveness information, meaning that early liveness is no longer the only source of liveness information in this function. This made it possible to hit an assert when early liveness was disabled via `DOTNET_JitEnableEarlyLivenessRange`. Remove the overeager assert and leave it up to the caller to ensure that there is valid liveness information (`GTF_VAR_DEATH`) when forward sub is invoked. Fix #90295
-
由 Lakshan Fernando 提交于
-
由 Jakob Botsch Nielsen 提交于
-
由 Johan Lorensson 提交于
Mono adopted PGO in .net7 as a replacement for a solution called profiled AOT in mono/mono used by Android SDK. In the replaced solution there was a concept of a stop trigger, meaning that the user could collect methods up to a stop trigger (a method name) meaning that the profiled AOT image would only include methods up to that point. When using EventPipe and nettrace there is limited ability to get the same fine grained control over what methods that ends up in the nettrace file. dotnet-monitor includes ways to stop tracing if it hits for example a specific method, but due to the nature of EventPipe, there could still be additional methods added to the trace when closing session. dotnet-trace currently don't offer any ability to do something similar, but if implemented, it would probably come with the same limitations as dotnet-monitor. Adding better filter capabilities to dotnet-pgo would add additional capabilities, giving users more control on what methods that gets included into the generated mibc file. That would give Mono's profiled AOT better control to include methods up to a stop trigger. dotnet-pgo alread had capabilities to include events based on timestamp interval. This commit extends that to select the lower/upper timestamp based on a regular expression matching methods. This commit also adds capabilities to add a method include/exclude filters using regular expression, giving users fine grained control on what methods to include/exclude in the generated mibc file. The additional filter capabilities could be used by Android SDK to for example create a mibc file including all methods up to Main, replacing the stop trigger features used in old profiled AOT solution. --------- Co-authored-by: Nmdh1418 <mitchhwang1418@gmail.com>
-
由 Kunal Pathak 提交于
* fix few scenarios for spillAlways() * Include JitStressRegs=0x800 * Revert "Include JitStressRegs=0x800" This reverts commit 170233235b3e24530386f48569a3e6f9d1de2b70.
-
由 Matous Kozak 提交于
* Extract MSB amd64 * add SSSE3 check
-
由 Miha Zupan 提交于
* Report exception type name in Http metrics * Mention 'Unknown' in a comment instead
-
由 Mark Plesko 提交于
-
由 Andy Gocke 提交于
--flat is a diagnostic-only option and not fully supported. It can still be specified if necessary through the DsymUtilOptions property and NativeSymbolExt property, but it will no longer be the default.
-
由 Aaron Robinson 提交于
-
由 Steve Pfister 提交于
A few System.Formats.Tar tests are failing due to the length of the path exceeding the limit. Additionally, other customer scenario tests that we don't need to run on mobile configurations weren't being skipped, but now are.
-