2 ms·

Impressive technical work and authorship. My quibble, which seems significant in context, is what happened with AoT?

• CurtHagenlocher 19d ago
  AoT is still a thing. Presumably a lot of the JIT improvements would also improve the generation of AoT-compiled code.
  • mlhpdx 19d ago
    I hope that’s the case but I’d feel a lot better to see it in print.
    • rsalus 19d ago
      do you mean NativeAoT? it's mentioned a few times in the post
• qingcharles 19d ago
  It still exists, it's still a bit quirky because of the way you need to match CPU to binary (e.g. some opcode extensions only existing on some CPUs)
• kg 19d ago
  AoT uses the same codegen (mostly) as the JIT so if you see a JIT improvement it's possible NativeAOT/ilc picked up that improvement too. Unless it's a runtime-only optimization, like guarded devirtualization... there's no straightforward way for an AOT compiler to do that without profiling data.
• drewnoakes 17d ago
  Native AOT is seeing a lot of use within Microsoft products too. Some bits of the .NET SDK use it, and C# Dev Kit (the C# extension for VS Code) uses it extensively in version 11. It brings a lot of performance to .NET.