Skip to content
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

.NET 4.8 Release Notes don't detail the JIT changes #1038

Open
marksmeltzer opened this issue May 15, 2019 · 1 comment
Open

.NET 4.8 Release Notes don't detail the JIT changes #1038

marksmeltzer opened this issue May 15, 2019 · 1 comment
Labels

Comments

@marksmeltzer
Copy link

marksmeltzer commented May 15, 2019

The announcement for .NET 4.8 (https://devblogs.microsoft.com/dotnet/announcing-the-net-framework-4-8/) says the following:

New Features in .NET Framework 4.8
Runtime – JIT improvements
The JIT in .NET 4.8 is based on .NET Core 2.1. All bug fixes and many code generation-based performance optimizations from .NET Core 2.1 are now available in the .NET Framework.

However, the release notes (https://github.com/microsoft/dotnet/blob/master/releases/net48/dotnet48-changes.md) don't have any of the details on the JIT changes...

For instance, I have posted an issue in the CLR project asking about optimizing away init locks for static initializers post init using progressive JIT (https://github.com/dotnet/coreclr/issues/24571). I was told in that issue by @jkotas that the requested feature already exists in .NET Core -- was it included in these JIT improvements for .NET 4.8? @jkotas has already answered, "No.", to that question. Fine. However, I would like to know which JIT changes from .NET Core were included in .NET 4.8.

@jkotas
Copy link
Member

jkotas commented May 15, 2019

However, I would like to know which JIT changes from .NET Core

All JIT changes from .NET Core 2.1 were integrated into .NET Framework 4.8.

Note that the improvements that required a supporting runtime changes outside the JIT itself were not included in .NET Framework 4.8 because they have high risk of breaking existing applications. The feature you are asking about is in this category.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants