-
Notifications
You must be signed in to change notification settings - Fork 4.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Publish NativeAOT compiler with NativeAOT #67742
Comments
This is the same configuration that we ship crossgen2 with. It produces a lot smaller packages with faster startup time. Setting this as `CoreCLRILCompilerDir` ensures that this is the ILCompiler that we test, build crossgen2 with, and package. I don't have high confidence that we can get dotnet#67742 in time for .NET 7 but since we still have some runway before .NET 7 snaps, checking this in as a plan B. This change is temporary until dotnet#67742 is fixed.
This is the same configuration that we ship crossgen2 with. It produces a lot smaller packages with faster startup time. Setting this as `CoreCLRILCompilerDir` ensures that this is the ILCompiler that we test, build crossgen2 with, and package. I don't have high confidence that we can get #67742 in time for .NET 7 but since we still have some runway before .NET 7 snaps, checking this in as a plan B. This change is temporary until #67742 is fixed.
FWIW aside from the work on getting the .csproj do the bootstrapping and publishing it seems to work. I compiled the |
Yes, that's basically where all the work is. We need to build with the live built compiler/runtime/libs, which makes things harder. Crossgen2 is already on that plan, but it's not straightforward to reuse that: https://github.com/dotnet/runtime/pull/67636/files |
It's quite reusable for the second step. Once you have some |
This work has been done |
This was tracking publishing with the live bits - without doing that, we'll still have issues like a couple months ago when we had to wait an extra release for the libc version switch to take effect because we're using lkg. We can say we're fine with that but wanted to call it out. |
Once crossgen2 is published with NativeAOT, we should publish the NativeAOT compiler the same way to keep them in sync.
The text was updated successfully, but these errors were encountered: