This repository has been archived by the owner on Nov 1, 2020. It is now read-only.
Add GC source files #1
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
All files have been copied from the coreclr repo (https://github.com/dotnet/coreclr/tree/master/src/gc) based on the commit label 8ff2389204d7c41b17eff0e9536267aea8d6496f.
|
👍 |
This was referenced Jan 27, 2016
MichalStrehovsky
pushed a commit
that referenced
this pull request
Jan 27, 2017
…me to store the address of the method to be called in a FuncEval. [tfs-changeset: 1645909]
ghost
mentioned this pull request
trylek
added a commit
that referenced
this pull request
Jul 20, 2018
* CorInfoImpl refactoring part #1 1) Refactor ComputeLookup to pass around references to the CORINFO_RESOLVED_TOKEN instead of its tokenContext. This will be needed in the next change to implement R2R variants of the methods. 2) Add new CanInline method to the Compilation class to be used by CorInfoImpl to query inline-ability. Thanks Tomas * Remove superfluous "using Internal.JitInterface" from CorInfoImpl
jkotas
pushed a commit
that referenced
this pull request
Aug 21, 2018
The ProjectN compiler never finishes compiling an app from an external use. The issue turns out to be due to the debug recording generation for a huge generic expansion. There are actually two problems: 1. The generic complexity computation is improper for the huge generic expansion in the failing case. The complexity computed was 0 and the compiler didn’t know it’s huge. 2. We are missing the check against the generic complexity in some places where UDT debug records are prepared. Fixing #1 at this point is tricky since it may cause wide asm diffs where normal calls become USG calls. Fixing #2 means the UDT types in the debug$T section for huge generic instantiations will fall back to USG or canonical records, so will the debug$S records for associated static fields. The debug$T change should only affect native debugging. The debug$S change can affect managed debugging but only for huge generic instantiations. We've decided #2 is probably the less risky way to unblock the user in the next release and it's fixed by this change for both ProjectN and ProjectX. [tfs-changeset: 1711506]
dotnet-maestro-bot
pushed a commit
to dotnet-maestro-bot/corert
that referenced
this pull request
Sep 4, 2018
* Fix ServiceController name population perf * Split tests * Remove dead field * Remove new use of DangerousGetHandle * SafeHandle all the things! * VSB dotnet#1 * VSB dotnet#2 * Fix GLE * Initialize machineName in ctor * Test for empty name ex * Null names * Inadvertent edit * Unix build * Move interop into class * Reverse SafeHandle for HAllocGlobal * Fix tests * Disable test for NETFX * CR feedback * Pattern matching on VSB * Direct call * typo Signed-off-by: dotnet-bot <dotnet-bot@microsoft.com>
jkotas
pushed a commit
that referenced
this pull request
Sep 5, 2018
* Fix ServiceController name population perf * Split tests * Remove dead field * Remove new use of DangerousGetHandle * SafeHandle all the things! * VSB #1 * VSB #2 * Fix GLE * Initialize machineName in ctor * Test for empty name ex * Null names * Inadvertent edit * Unix build * Move interop into class * Reverse SafeHandle for HAllocGlobal * Fix tests * Disable test for NETFX * CR feedback * Pattern matching on VSB * Direct call * typo Signed-off-by: dotnet-bot <dotnet-bot@microsoft.com>
trylek
added a commit
that referenced
this pull request
Mar 19, 2019
This change enables parallelization of ILC compilation when building multiple assemblies. For the CoreCLR framework I'm observing about 3~4 times compilation time speedup (about 33 seconds where previously I was observing about 120 seconds with SuperIlc and about 180 seconds with the legacy scripts). As I've introduced a subfolder per compiler name (ilc / crossgen), I could relax the requirement for output directory specification (because it can default to the input folder) and the check for input folder being a subfolder of the output folder. Thanks Tomas P.S. I'm merging this in in spite of the lab failures because I'm 100% sure this change is not exercised by the lab in any manner and the lab has been known to be somewhat unstable recently.
jkotas
pushed a commit
that referenced
this pull request
Apr 25, 2019
…mation does not match the args (plus this if required) (#1)
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
All files have been copied from the coreclr repo
(https://github.com/dotnet/coreclr/tree/master/src/gc) based on the commit
label 8ff2389204d7c41b17eff0e9536267aea8d6496f.