VSadov/Satori
1
0
Fork 0
mirror of https://github.com/VSadov/Satori.git synced 2025-06-11 02:13:38 +09:00
Code Activity

Fix complus casing (#46167)

Browse source
This commit is contained in:
Dan Moseley 2020-12-16 16:45:32 -08:00 • committed by GitHub
parent 6f8ae8feb5
commit d3a04b2959
Signed by: github
GPG key ID: 4AEE18F83AFDEB23
3 changed files with 3 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

2
docs/design/coreclr/jit/lsra-detail.md
View file

@ -962,7 +962,7 @@ The following dumps and debugging modes are provided:
LSRA Stress Modes LSRA Stress Modes
----------------- -----------------
The implementation uses the `COMPLUS_JitStressRegs` environment variable. The implementation uses the `COMPlus_JitStressRegs` environment variable.
The following are the stress modes associated with this variable. For The following are the stress modes associated with this variable. For
the most part they can be combined, though in some cases the values are the most part they can be combined, though in some cases the values are
exclusive: exclusive:

2
docs/design/coreclr/jit/ryujit-tutorial.md
View file

@ -661,7 +661,7 @@ Recognize "Intrinsic" (SampleStep1 shelveset)
- instrsxarch.h: encoding - instrsxarch.h: encoding
- codegenxarch.cpp: generate instruction - codegenxarch.cpp: generate instruction
- importer.cpp: name recognition - importer.cpp: name recognition
- set COMPLUS_JitDump - set COMPlus_JitDump
- Run & capture jitdump2.out, search for CountBits, then look at disassembly - Run & capture jitdump2.out, search for CountBits, then look at disassembly
Add Pattern Recognition (SampleStep2 shelveset): Add Pattern Recognition (SampleStep2 shelveset):

2
docs/workflow/debugging/coreclr/debugging.md
View file

@ -100,7 +100,7 @@ Using Visual Studio
(Note: you probably want 'dotnet exec' rather than 'dotnet run' because the run verb is implemented to launch the app in a child-process and the debugger won't be attached to that child process) (Note: you probably want 'dotnet exec' rather than 'dotnet run' because the run verb is implemented to launch the app in a child-process and the debugger won't be attached to that child process)
- Working Directory: Make this match whatever you would have used on the command-line - Working Directory: Make this match whatever you would have used on the command-line
- Debugger Type: Set this to either 'Managed (CoreCLR)' or 'Native Only' depending on whether you want to debug the C+ or native code respectively. - Debugger Type: Set this to either 'Managed (CoreCLR)' or 'Native Only' depending on whether you want to debug the C+ or native code respectively.
- Environment: Add any environment variables you would have added at the command-line. You may also consider adding COMPLUS_ZapDisable=1 and COMPLUS_ReadyToRun=0 which disable NGEN and R2R pre-compilation respectively and allow the JIT to create debuggable code. This will give you a higher quality C# debugging experience inside the runtime framework assemblies, at the cost of somewhat lower app performance. - Environment: Add any environment variables you would have added at the command-line. You may also consider adding COMPlus_ZapDisable=1 and COMPlus_ReadyToRun=0 which disable NGEN and R2R pre-compilation respectively and allow the JIT to create debuggable code. This will give you a higher quality C# debugging experience inside the runtime framework assemblies, at the cost of somewhat lower app performance.
- For managed debugging, there are some settings in Debug->Options, Debugging->General that might be useful: - For managed debugging, there are some settings in Debug->Options, Debugging->General that might be useful:
- Uncheck 'Just My Code'. This will allow you debug into the framework libraries. - Uncheck 'Just My Code'. This will allow you debug into the framework libraries.
- Check 'Enable .NET Framework Source Stepping.' This will configure the debugger to download symbols and source automatically for runtime framework binaries. If you built the framework yourself this may be irrelevant because you already have all the source on your machine but it doesn't hurt. - Check 'Enable .NET Framework Source Stepping.' This will configure the debugger to download symbols and source automatically for runtime framework binaries. If you built the framework yourself this may be irrelevant because you already have all the source on your machine but it doesn't hurt.