Skip to content

Enable JitDisasm in Release - #73365

Merged
EgorBo merged 35 commits into
dotnet:mainfrom
EgorBo:jit-disasm-release
Aug 10, 2022
Merged

Enable JitDisasm in Release#73365
EgorBo merged 35 commits into
dotnet:mainfrom
EgorBo:jit-disasm-release

Conversation

@EgorBo

@EgorBoEgorBo commented Aug 4, 2022

Copy link
Copy Markdown
Member

This PR enables DOTNET_JitDisasm for Release config.

It doesn't print lcl tables, EH and gc info (for now).

Adds ~30kb to the binary size of jit.

The only noticeable impact on Release is that instrDesc struct is now 8bytes bigger (_idDebugOnlyInfo) - but I might fix it with a standalone hash-table which will be populated only when JitDisasm variable is not empty.

Example:

publicclassTests{staticintstaticField;stringinstanceField;publicvirtualvoidVirtualCall(){}publicvoidTest(string[]args,IDisposabled){// control flowif(args?.Length==0){Console.WriteLine("field: "+staticField);Console.WriteLine(instanceField);}else{// SIMD (data section)Console.WriteLine(Vector128.Create(1,2,3,4));}// Virtual callVirtualCall();// Interface calld?.Dispose();// Jump tableswitch(args.Length){case1:Console.WriteLine("1");break;case2:Console.WriteLine("2");break;case3:Console.WriteLine("3");break;case4:Console.WriteLine("5");break;case6:Console.WriteLine("7");break;}Console.ReadKey();}}

DOTNET_JitDisasm=Test: (DOTNET_JitDiffableDasm is 0 by default, hence, raw bytes, addresses)

; Assembly listing for method Tests:Test(ref,IDisposable):this; Emitting BLENDED_CODE for X64 CPU with AVX - Windows; optimized code; rsp based frame; partially interruptible; No PGO data; 0 inlinees with PGO data; 2 single block inlinees; 0 inlinees without PGO dataG_M000_IG01: ;; offset=0000H57pushrdi56pushrsi53pushrbx 4883EC30 subrsp,48 C5F877 vzeroupper 488BF1 movrsi,rcx 488BFA movrdi,rdx 498BD8 movrbx,r8G_M000_IG02: ;; offset=0013H 4885FF testrdi,rdi 743D je SHORT G_M000_IG04G_M000_IG03: ;; offset=0018H 837F0800 cmp dword ptr [rdi+8],07537jne SHORT G_M000_IG04 8B0DF8B40C00 movecx, dword ptr [(reloc 0x7ffd9745c06c)] FF15560A1100 call[Number:Int32ToDecStr(int):String] 488BD0 movrdx,rax 48B9D820804A0C020000 movrcx,0x20C4A8020D8 488B09 movrcx, gword ptr [rcx] FF15D0100900 call[String:Concat(String,String):String] 488BC8 movrcx,rax FF15FFAE0F00 call[Console:WriteLine(String)] 488B4E08 movrcx, gword ptr [rsi+8] FF15F5AE0F00 call[Console:WriteLine(String)] EB27 jmp SHORT G_M000_IG05G_M000_IG04: ;; offset=0055H 48B978D64797FD7F0000 movrcx,0x7FFD9747D678 E8FCAEAE5F call CORINFO_HELP_NEWSFAST C5F91005E4000000 vmovupdxmm0, xmmword ptr [reloc @RWD00] C5F9114008 vmovupd xmmword ptr [rax+8],xmm0 488BC8 movrcx,rax FF15B6AE0F00 call[Console:WriteLine(Object)]G_M000_IG05: ;; offset=007AH 488BCE movrcx,rsi 488B06 movrax, qword ptr [rsi] 488B4040 movrax, qword ptr [rax+64] FF5020 call[rax+32]Tests:VirtualCall():this 4885DB testrbx,rbx7410je SHORT G_M000_IG07G_M000_IG06: ;; offset=008CH 488BCB movrcx,rbx 49BB08001E97FD7F0000 movr11,0x7FFD971E0008 41FF13 call[r11]IDisposable:Dispose():thisG_M000_IG07: ;; offset=009CH 8B4F08 movecx, dword ptr [rdi+8] FFC9 dececx 83F905 cmpecx,5 0F877F000000 ja G_M000_IG13 8BC9 movecx,ecx 488D05AD000000 learax,[reloc @RWD16] 8B0488 moveax, dword ptr [rax+4*rcx] 488D1556FFFFFF leardx, G_M000_IG02 4803C2 addrax,rdx FFE0 jmpraxG_M000_IG08: ;; offset=00C2H 48B9E020804A0C020000 movrcx,0x20C4A8020E0 488B09 movrcx, gword ptr [rcx] FF1573AE0F00 call[Console:WriteLine(String)] EB52 jmp SHORT G_M000_IG13G_M000_IG09: ;; offset=00D7H 48B9E820804A0C020000 movrcx,0x20C4A8020E8 488B09 movrcx, gword ptr [rcx] FF155EAE0F00 call[Console:WriteLine(String)] EB3D jmp SHORT G_M000_IG13G_M000_IG10: ;; offset=00ECH 48B9F020804A0C020000 movrcx,0x20C4A8020F0 488B09 movrcx, gword ptr [rcx] FF1549AE0F00 call[Console:WriteLine(String)] EB28 jmp SHORT G_M000_IG13G_M000_IG11: ;; offset=0101H 48B9F820804A0C020000 movrcx,0x20C4A8020F8 488B09 movrcx, gword ptr [rcx] FF1534AE0F00 call[Console:WriteLine(String)] EB13 jmp SHORT G_M000_IG13G_M000_IG12: ;; offset=0116H 48B90021804A0C020000 movrcx,0x20C4A802100 488B09 movrcx, gword ptr [rcx] FF151FAE0F00 call[Console:WriteLine(String)]G_M000_IG13: ;; offset=0129H 488D4C2420 learcx, bword ptr 33D2 xoredx,edx FF158AEE0F00 call[ConsolePal:ReadKey(bool):ConsoleKeyInfo]90nopG_M000_IG14: ;; offset=0137H 4883C430 addrsp,48 5B poprbx 5E poprsi 5F poprdi C3 retRWD00 dq 0000000200000001h,0000000400000003hRWD16 dd 000000AFh ; case G_M000_IG08dd000000C4h ; case G_M000_IG09dd000000D9h ; case G_M000_IG10dd000000EEh ; case G_M000_IG11dd00000116h ; case G_M000_IG13dd00000103h ; case G_M000_IG12; Total bytes of code 319

@ghostghost added the area-CodeGen-coreclr CLR JIT compiler in src/coreclr/src/jit and related components such as SuperPMI label Aug 4, 2022
@ghostghost assigned EgorBoAug 4, 2022
@ghost

ghost commented Aug 4, 2022

Copy link
Copy Markdown

Tagging subscribers to this area: @JulieLeeMSFT, @jakobbotsch
See info in area-owners.md if you want to be subscribed.

Issue Details

This PR enables DOTNT_JitDisasm, DOTNET_NgenDisasm and DOTNET_JitDiffableDasm for Release config.

It doesn't print lcl tables and gc info (for now).

Adds ~30kb to the binary size of jit.

The only noticeable impact on Release is that instrDesc struct is now 8bytes bigger (_idDebugOnlyInfo) - but I might fix it with a standalone hash-table which will be populated only when JitDisasm variable is not empty.

Example:

publicclassTests{staticintstaticField;stringinstanceField;publicvirtualvoidVirtualCall(){}publicvoidTest(string[]args,IDisposabled){// control flowif(args?.Length==0){Console.WriteLine("field: "+staticField);Console.WriteLine(instanceField);}else{// SIMD (data section)Console.WriteLine(Vector128.Create(1,2,3,4));}// Virtual callVirtualCall();// Interface calld?.Dispose();// Jump tableswitch(args.Length){case1:Console.WriteLine("1");break;case2:Console.WriteLine("2");break;case3:Console.WriteLine("3");break;case4:Console.WriteLine("5");break;case6:Console.WriteLine("7");break;}Console.ReadKey();}}
; Emitting BLENDED_CODE for X64 CPU with AVX - Windows; optimized code; rsp based frame; partially interruptible; No PGO data; 0 inlinees with PGO data; 2 single block inlinees; 0 inlinees without PGO dataIG_01:57pushrdi56pushrsi53pushrbx 4883EC30 subrsp,48 C5F877 vzeroupper 488BF1 movrsi,rcx 488BFA movrdi,rdx 498BD8 movrbx,r8IG_02: 4885FF testrdi,rdi 743D je SHORT G_M000_IG04IG_03: 837F0800 cmp dword ptr [rdi+8],07537jne SHORT G_M000_IG04 8B0DF8B40C00 movecx, dword ptr [(reloc 0x7ffd2d2dc06c)] FF15560A1100 call[Number:Int32ToDecStr(int):String] 488BD0 movrdx,rax 48B9D820C0EF74020000 movrcx,0x274EFC020D8 488B09 movrcx, gword ptr [rcx] FF15D0100900 call[String:Concat(String,String):String] 488BC8 movrcx,rax FF15FFAE0F00 call[Console:WriteLine(String)] 488B4E08 movrcx, gword ptr [rsi+8] FF15F5AE0F00 call[Console:WriteLine(String)] EB27 jmp SHORT G_M000_IG05IG_04: 48B978D62F2DFD7F0000 movrcx,0x7FFD2D2FD678 E8FCAEAF5F call CORINFO_HELP_NEWSFAST C5F91005E4000000 vmovupdxmm0, xmmword ptr [reloc @RWD00] C5F9114008 vmovupd xmmword ptr [rax+8],xmm0 488BC8 movrcx,rax FF15B6AE0F00 call[Console:WriteLine(Object)]IG_05: 488BCE movrcx,rsi 488B06 movrax, qword ptr [rsi] 488B4040 movrax, qword ptr [rax+64] FF5020 call[rax+32]Tests:VirtualCall():this 4885DB testrbx,rbx7410je SHORT G_M000_IG07IG_06: 488BCB movrcx,rbx 49BB0800062DFD7F0000 movr11,0x7FFD2D060008 41FF13 call[r11]IDisposable:Dispose():thisIG_07: 8B4F08 movecx, dword ptr [rdi+8] FFC9 dececx 83F905 cmpecx,5 0F877F000000 ja G_M000_IG13 8BC9 movecx,ecx 488D05AD000000 learax,[reloc @RWD16] 8B0488 moveax, dword ptr [rax+4*rcx] 488D1556FFFFFF leardx, G_M000_IG02 4803C2 addrax,rdx FFE0 jmpraxIG_08: 48B9E020C0EF74020000 movrcx,0x274EFC020E0 488B09 movrcx, gword ptr [rcx] FF1573AE0F00 call[Console:WriteLine(String)] EB52 jmp SHORT G_M000_IG13IG_09: 48B9E820C0EF74020000 movrcx,0x274EFC020E8 488B09 movrcx, gword ptr [rcx] FF155EAE0F00 call[Console:WriteLine(String)] EB3D jmp SHORT G_M000_IG13IG_10: 48B9F020C0EF74020000 movrcx,0x274EFC020F0 488B09 movrcx, gword ptr [rcx] FF1549AE0F00 call[Console:WriteLine(String)] EB28 jmp SHORT G_M000_IG13IG_11: 48B9F820C0EF74020000 movrcx,0x274EFC020F8 488B09 movrcx, gword ptr [rcx] FF1534AE0F00 call[Console:WriteLine(String)] EB13 jmp SHORT G_M000_IG13IG_12: 48B90021C0EF74020000 movrcx,0x274EFC02100 488B09 movrcx, gword ptr [rcx] FF151FAE0F00 call[Console:WriteLine(String)]IG_13: 488D4C2420 learcx, bword ptr 33D2 xoredx,edx FF158AEE0F00 call[ConsolePal:ReadKey(bool):ConsoleKeyInfo]90nopIG_14: 4883C430 addrsp,48 5B poprbx 5E poprsi 5F poprdi C3 retRWD00 dq 0000000200000001h,0000000400000003hRWD16 dd 000000AFh ; case IG_08dd000000C4h ; case IG_09dd000000D9h ; case IG_10dd000000EEh ; case IG_11dd00000116h ; case IG_13dd00000103h ; case IG_12; Total bytes of code 319
Author:EgorBo
Assignees:-
Labels:

area-CodeGen-coreclr

Milestone:-

@stephentoub

Copy link
Copy Markdown
Member

This would be super helpful.

Comment threadsrc/coreclr/jit/emitxarch.cpp Outdated
@hez2010

Copy link
Copy Markdown
Contributor

Does this PR also cover crossgen2?

@EgorBo

Copy link
Copy Markdown
MemberAuthor

Does this PR also cover crossgen2?

Yes works for R2R. And, probably, for NativeAOT as well but afair it redirects stdout cc @MichalStrehovsky

@EgorBo

Copy link
Copy Markdown
MemberAuthor

One noticeable advantage over sharplab for end-users is the ability to print names for helper calls, e.g.

publicclassC{objecto;publicvoidM(object[]a){a[0]=42;o=a;}}

Sharplab:

image

JitDisasm:

; Assembly listing for method C:M(ref):this; Emitting BLENDED_CODE for X64 CPU with AVX - Windows; optimized code; rsp based frame; partially interruptible; No PGO dataG_M000_IG01: ;; offset=0000H57pushrdi56pushrsi 4883EC28 subrsp,40 488BF9 movrdi,rcx 488BF2 movrsi,rdxG_M000_IG02: ;; offset=000CH 48B958E4DC2CFD7F0000 movrcx,0x7FFD2CDCE458 E835AFB15F call CORINFO_HELP_NEWSFAST C740082A000000 mov dword ptr [rax+8],42 4C8BC0 movr8,rax 488BCE movrcx,rsi 33D2 xoredx,edx E891F4FFFF call CORINFO_HELP_ARRADDR_ST 488D4F08 learcx, bword ptr [rdi+8] 488BD6 movrdx,rsi E875F4E2FF call CORINFO_HELP_ASSIGN_REF90nopG_M000_IG03: ;; offset=003CH 4883C428 addrsp,40 5E poprsi 5F poprdi C3 ret; Total bytes of code 67

Perhaps, it will be useful for sharplab too

@JulieLeeMSFT

Copy link
Copy Markdown
Member

@EgorBo do you plan to merge this to .NET 7?

@EgorBo

Copy link
Copy Markdown
MemberAuthor

@EgorBo do you plan to merge this to .NET 7?

It probably does not meet the bar but I'd love to merge it in .NET 7.0, but no strong opinion

@stephentoub

stephentoub commented Aug 4, 2022

Copy link
Copy Markdown
Member

It probably does not meet the bar but I'd love to merge it in .NET 7.0, but no strong opinion

FWIW, I would love that, too :) (as long as there's no meaningful perf regressions associated with it and there are no concerns about the data this exposes).

@EgorBo

Copy link
Copy Markdown
MemberAuthor

no concerns about the data this exposes

Yep, we discussed this one too and came to conclusion that there is nothing to be afraid of and our competitors provide this ability too

@jkotas

Copy link
Copy Markdown
Member

Does this PR also cover crossgen2?

Yes works for R2R. And, probably, for NativeAOT

NativeAOT compiler and crossgen use exact same infrastructure. If it works for one, it should work for the other one too.

You have to specify the option on the command line instead of env variable. Is that correct?

DOTNET_NgenDisasm

We should not be injecting new life into NGen name. Can we rename this so that it does not have NGen in the name?

I am wondering why we need both NgenDisasm and JitDisasm. Can we have just one that kicks in everywhere?

@EgorBo

Copy link
Copy Markdown
MemberAuthor

You have to specify the option on the command line instead of env variable. Is that correct?

Correct, e.g. --codegenopt NgenDisasm="Test"

We should not be injecting new life into NGen name. Can we rename this so that it does not have NGen in the name?

I fully agree, should I still keep NgenDisasm for backward compatibility?

@jkotas

Copy link
Copy Markdown
Member

I fully agree, should I still keep NgenDisasm for backward compatibility?

There is no backward compatibility to be worried about. We should delete all configs that start with NGen and use the Jit configs everywhere.

If we have any infra that use the NGen configs (I do not see any), it needs to be updated.

I see a few places that clear COMPlus_Ngen* in superpmi. They should be deleted. They are not doing anything useful anyway since NGen configs are not read from the environment.

@EgorBo

EgorBo commented Aug 4, 2022

Copy link
Copy Markdown
MemberAuthor

There is no backward compatibility to be worried about.

https://godbolt.org/ relies on it to print ASM for C#, but I assume it will only benefit from moving to release .NET as it won't have to compile .NET from sources and use public previews/daily builds of Release .NET instead cc @hez2010

@EgorBo
EgorBoforce-pushed the jit-disasm-release branch from 2849219 to 98a2a9dCompareAugust 4, 2022 13:57
@EgorBoEgorBo added this to the 7.0.0 milestone Aug 4, 2022
Comment threadsrc/coreclr/jit/compiler.cpp
@hez2010

hez2010 commented Aug 4, 2022

Copy link
Copy Markdown
Contributor

There is no backward compatibility to be worried about.

https://godbolt.org/ relies on it to print ASM for C#.

There is nothing to worry about. We can definitely setup a new net7.0 config for godbolt while keeping net6.0 as is.

@EgorBo

Copy link
Copy Markdown
MemberAuthor

Outerloop pipelines failures seem unrelated:

@jakobbotsch

Copy link
Copy Markdown
Member

I have started a non-PR run of runtimehere, which will get us some more coverage for release JIT with the libraries tests.

The change is somewhat low risk for release since when m_debugInfoSize = 0, the layout just collapses back to what it was before. So even if we forgot to account for it somewhere, it is unlikely that will cause problems for release non-disasm builds.

My main concern would be that we have an idDebugOnlyInfo() use somewhere that is not conditioned on the debug info being present, but I've audited the uses and wasn't able to find any way that could happen.

@EgorBo

Copy link
Copy Markdown
MemberAuthor

My main concern would be that we have an idDebugOnlyInfo() use somewhere that is not conditioned on the debug info being present, but I've audited the uses and wasn't able to find any way that could happen.

Right, I audited those too (and inserted a failfast if we entered them with .disAsm = false) locally

@EgorBo

Copy link
Copy Markdown
MemberAuthor

@dotnet/jit-contrib @jakobbotsch@BruceForstall PTAL

@AndyAyersMS

Copy link
Copy Markdown
Member

Seems like we should allow users to specify JitDiffableDasm too?

If you are live debugging it would be nice to see the actual addresses and such.

#ifdef DEBUG
// Should we make it diffable?
disDiffable = disComp->opts.dspDiffable;
#else// !DEBUG
// NOTE: non-debug builds are always diffable!
disDiffable = true;
#endif// !DEBUG

Might also be nice to be able to control JitDasmWithAddress and JitDasmWithAlignmentBoundaries and perhaps even JitDisasmWithGC and JitDisasmWithDebugInfo.

There are a whole bunch more like this: unwind, eh, ... but they might take a lot more work.

@omariom

Copy link
Copy Markdown
Contributor

@EgorBo
Can we assume that it will always start with "; Assembly listing for method " and end with "; Total bytes of code "?

@EgorBo

Copy link
Copy Markdown
MemberAuthor

Seems like we should allow users to specify JitDiffableDasm too?

If you are live debugging it would be nice to see the actual addresses and such.

#ifdef DEBUG
// Should we make it diffable?
disDiffable = disComp->opts.dspDiffable;
#else// !DEBUG
// NOTE: non-debug builds are always diffable!
disDiffable = true;
#endif// !DEBUG

Might also be nice to be able to control JitDasmWithAddress and JitDasmWithAlignmentBoundaries and perhaps even JitDisasmWithGC and JitDisasmWithDebugInfo.

There are a whole bunch more like this: unwind, eh, ... but they might take a lot more work.

Yes, I had to draw the line somewhere for the initial impl since, obviously, supporting all of them is a lot more work, I am going to take a look at JitDiffableDasm separately if you don't mind. JitDasmWithAlignmentBoundaries is also nice to have - it draws nice lines 😄

@EgorBo

EgorBo commented Aug 8, 2022

Copy link
Copy Markdown
MemberAuthor

@EgorBo Can we assume that it will always start with "; Assembly listing for method " and end with "; Total bytes of code "?

Good question, I assume some 3rd party tools are going to depend on it (parse) and we should not ever change it
So I personally is fine with the current format, if anyone has better ideas - feel free to change now

@MichalPetryka

MichalPetryka commented Aug 8, 2022

Copy link
Copy Markdown
Contributor

@EgorBo Can we assume that it will always start with "; Assembly listing for method " and end with "; Total bytes of code "?

Good question, I assume some 3rd party tools are going to depend on it (parse) and we should not ever change it So I personally is fine with the current format, if anyone has better ideas - feel free to change now

There could be a separate env var that'd enable a special stable parsable output, something like git does for tools invoking it.

@BruceForstallBruceForstall left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good. It would be nice if the number of places doing + m_debugInfoSize were more minimized, via wrapper functions or the like.

It would also be nice if some of the additional controls were available, as previously suggested, like JitStdOutFile, JitDiffableDasm, etc.

#endif // MULTIREG_HAS_SECOND_GC_RET
};

// TODO-Cleanup: Uses of stack-allocated instrDescs should be refactored to be unnecessary.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why should we eliminate stack-allocated instrDescs? It seems perfectly reasonable to allow them.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We are creating these temporary instrDesc simply to be able to call existing methods to emit code/do printing. That seems like a code smell that the codegen/printing methods themselves should be refactored so that we can use the specific parts we want directly instead of having to indirect through an instrDesc structure. BTW, there's just three uses of this pattern:

  • One in emitxarch.cpp that wants to call an emit method. It already has this same cleanup comment.
  • One in emitarm.cpp and emitarm64.cpp for printing LARGEJMP instructions.

{
private:
instrDescDebugInfo* idDebugInfo;
alignas(alignof(T)) char idStorage[sizeof(T)];

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Given the static_assert_no_msg below, isn't this alignas not useful? Or equivalent to alignas(sizeof(instrDescDebugInfo*))?

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In theory, some future instrDesc could have larger-than-pointer alignment requirement. That would certainly require some work to support and I just want it to be noisy that this is a place that would need to be fixed.

@kunalspathak

Copy link
Copy Markdown
Contributor

Started to review, but it seems we are not printing PerfScore yet?

@kunalspathak

Copy link
Copy Markdown
Contributor

It would be nice if the number of places doing + m_debugInfoSize were more minimized, via wrapper functions or the like.

I agree with @BruceForstall . There are too many places where we are doing + m_debugInfoSize and it is easy to forget doing that in future. A wrapper function will be helpful.

@kunalspathakkunalspathak left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM.

Consolidate most uses of m_debugInfoSize into these functions.
@jakobbotsch

Copy link
Copy Markdown
Member

I pushed a commit that adds emitFirstInstrDesc and emitAdvanceInstrDesc and uses these in place of the manual castto/buffer accesses, which consolidates most uses of m_debugInfoSize.

@kunalspathakkunalspathak left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Comment threadsrc/coreclr/jit/emit.cpp Outdated
@BruceForstall

Copy link
Copy Markdown
Contributor

I pushed a commit that adds emitFirstInstrDesc and emitAdvanceInstrDesc and uses these in place of the manual castto/buffer accesses, which consolidates most uses of m_debugInfoSize.

The functions are a nice improvement.

@jakobbotsch

Copy link
Copy Markdown
Member

Does the JIT dll import table change? (I.e., are there any new dependencies in the Release build?)

We get two new IAT entries on Windows: __stdio_common_vsprintf_s and strnlen.

@EgorBo

Copy link
Copy Markdown
MemberAuthor

Merging now. We're going to keep eyes on TP-related benchmarks (e.g. "Crossgen2 Throughput Trends" page) in coming weeks.

Kudos to @jakobbotsch for mitigating all the initial TP/Memory regressions 🎉

@EgorBo
EgorBo merged commit 87d5ece into dotnet:mainAug 10, 2022
@ghostghost locked as resolved and limited conversation to collaborators Sep 9, 2022
Sign up for freeto subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

area-CodeGen-coreclrCLR JIT compiler in src/coreclr/src/jit and related components such as SuperPMI

Projects

None yet

Development

Successfully merging this pull request may close these issues.

12 participants

@EgorBo@stephentoub@hez2010@JulieLeeMSFT@jkotas@jakobbotsch@SingleAccretion@BruceForstall@AndyAyersMS@omariom@MichalPetryka@kunalspathak