Considerably speed up building the test tree on Windows#82080
Considerably speed up building the test tree on Windows#82080MichalStrehovsky wants to merge 1 commit intodotnet:mainfrom
Conversation
Building the JIT\Directed tree on my machine before: 5 minutes 7 seconds. After: 3 minutes 34 seconds.
|
Tagging subscribers to this area: @agocke, @MichalStrehovsky, @jkotas Issue DetailsBuilding the JIT\Directed tree on my machine: Before: 5 minutes 7 seconds. Not kidding. We run vswhere and vcvarsall. My bet is on vcvarsall - opening the visual studio tools command prompt always takes an eternity. Cc @dotnet/ilc-contrib
|
|
Hm, so one issue I just ran into with this is: The The repo builds with x86_amd64 cross linker (#76516). The linker ILC would set up is the amd64 native linker. I'm converting this to draft while I meditate on this. It's possible the compile time wins are also due to using the x86 linker. But also if there's stability issues, there's little point in doing this :( |
|
Also, do instructions for running individual tests need updating for this change? https://github.com/dotnet/runtime/blob/main/docs/workflow/building/coreclr/nativeaot.md#running-tests |
|
We can only do this if #76516 is fixed. |
Building the JIT\Directed tree on my machine:
Before: 5 minutes 7 seconds.
After: 3 minutes 34 seconds.
Not kidding.
We run vswhere and vcvarsall. My bet is on vcvarsall - opening the visual studio tools command prompt always takes an eternity.
Cc @dotnet/ilc-contrib