Jan Kotas

There are multiple possible implementation strategies. It can either be implemented in the runtimes in C/C++ and/or it can be must-expand intrinsic in the JIT.

@AaronRobinsonMSFT Could you please take a look? The `SafeHandle.handle` is a good value (00000000000000A3), but it somehow turned into -1 by the time it got into the P/Invoke.

cc @noahfalk @kouvel

I have reverted the offending change in https://github.com/dotnet/runtime/pull/73476 .

> Is it reasonable to expect the linker not to make branches like this? No. This is a bug in the linker that needs to be fixed.

I am not aware of any library like that. I think that the best path to enable this would be to enhance clrmd to understand NativeAOT.

There are tools for dumping binaries disassembly: `dumpbin` on Windows and `objdump` on Unix. I do not think we would want to the AOT compiler to carry the disassembler with...

JitDump is not available in shipping JIT binary.

> We could potentially have a compiler switch to dump the decoder ring into a file FWIW, we will need to do something like this if we get serious about...

We do not have that today. It would require duplicating the runtime hardware capabilities detection in the AOT compiler, or somehow getting access to the runtime detection logic, The AOT...