DOTNET_JitDisasmSummary=1 proved itself as a useful a quick (in comparison with dotnet trace) tool to obtain stats about JIT: how many methods are jitted, how many of those are of a specific tier, names, etc.
I propose to introduce the same for R2R code, something like this:
DOTNET_R2RSummary=1:
1: R2R used for Tables:GetBucket(int):byref:this [IL size=49, code size=294]
2: R2R used for ConcurrentDictionary`2:TryGetValue(Key,byref):bool:this [IL size=49, code size=294]
3: R2R rejected for Dictionary`2:.ctor():this [IL size=9, code size=36, reason="version is too old"]
with ability to log failing attempts. In theory, it can be merged with JitDisasmSummary if needed. but I'd prefer not to - currently, JitDisasmSummary prints just 7 entries for Hello World while with R2R it will be hundreds so user's code will be lost in there.
DOTNET_JitDisasmSummary=1proved itself as a useful a quick (in comparison withdotnet trace) tool to obtain stats about JIT: how many methods are jitted, how many of those are of a specific tier, names, etc.I propose to introduce the same for R2R code, something like this:
DOTNET_R2RSummary=1:with ability to log failing attempts. In theory, it can be merged with JitDisasmSummary if needed. but I'd prefer not to - currently, JitDisasmSummary prints just 7 entries for Hello World while with R2R it will be hundreds so user's code will be lost in there.