-
Notifications
You must be signed in to change notification settings - Fork 523
Kestrel Dasm #1058
Comments
Cool. How did you create the ngen dasm? |
Twist on dotnet/coreclr#6634 (comment) Prep
Iterations
The command: jit-dasm --platform MyApp\bin\Release\netcoreapp1.0\win7-x64\publish --base MyApp\bin\Release\netcoreapp1.0\win7-x64\publish\crossgen.exe --output M:\output\KDNEW MyApp\bin\Release\netcoreapp1.0\win7-x64\publish\Microsoft.AspNetCore.Server.Kestrel.dll Would create a dasm file for Microsoft.AspNetCore.Server.Kestrel in |
New info... so if you do the standalone app + publish, then copy the checked clrjit.dll over (Prep) Then you can just set the Since its actually running it will take the vectors paths etc... |
Also if you set |
Ok simplest path... Build coreclr checked and release (can keep using these till you want an new update of coreclr) coreclr> Build test app as win7-x64 standalone and publish Copy all files from Copy Set the enviorment vars Run your standalone exe from the publish directory probably piping its output to a file You can also get the jit to only output a certain disassembly e.g. The jit will work in parallel, so wait for start up to complete before you try loading a page or the output will get interleaved. |
Produced this while looking at something else; might be interesting
Its ngen'd so caveats apply; Vector paths aren't taken and readonly statics aren't consts etc...
https://aoa.blob.core.windows.net/aspnet/Microsoft.AspNetCore.Server.Kestrel.dasm.txt
But should give flavour for what's inlined what's not, how things expand, what is converted to registers what not and why etc...
/cc @davidfowl @halter73 @CesarBS
The text was updated successfully, but these errors were encountered: