Can anyone suggest a way (supported or unsupported) of getting a look at native code bytes compiled by the NETCF JIT compiler. I happen to be on WinCE6.0 on an ARM platform.
I'm guessing that this can be done with a native debugger, but I'm trying to figure out (essentially) how I would get my bearings to know what I'm looking at. Perhaps one could set a breakpoint in a P/Invoke call, and then step back into JITted managed code - the trick being knowing when you return to a particular routine that you're interested in.
My purpose is to determine why (in my case), JITted math code performance is significantly worse than equivalent C++ (native) code. And yes, I'm aware that .NETCF doesn't have native floating point support.