Tightened Hardware Baseline, New Runtime Async in .NET 11
.NET 11 updates minimum hardware requirements to align with current operating system baselines. x86/x64 systems now require x86-64-v2 baseline capabilities (up from v1), ensuring support for SSE3, SSSE3, and SSE4 instructions. ReadyToRun targets on Windows and Linux move to x86-64-v3, unlocking AVX, AVX2, and related instruction sets. ARM64 devices on Windows must support LSE instructions. These changes trim maintenance burden from the runtime codebase, though compatibility drops for older hardware.
Runtime Async V2 fundamentally changes how asynchronous execution works—the runtime now handles suspension and resumption instead of the compiler generating state-machine infrastructure. The benefit is immediately visible in stack traces: profilers and debuggers see actual method calls rather than machine-generated scaffolding. A sample async call chain in the documentation illustrates the gain: 13 stack frames collapse to 5 with Runtime Async enabled. Projects can opt in with <Features>runtime-async=on</Features>. The .NET runtime libraries ship with this setting active, making it practical to migrate entire applications. The approach also enables better inlining during ReadyToRun compilation and fixes covariant Task returns in virtual method dispatch.
Read the full article
Continue reading at Hacker News →This is an AI-generated summary. Read the original for the full story.