JIT: Double check lvHasExplicitInit when resuming runtime async functions #126750

Activity

1. dotnet-policy-service

   added

   untriagedNew issue has not been triaged by the area ownerNew issue has not been triaged by the area owner

   on Apr 10, 2026
2. jakobbotsch

   self-assigned this

   on Apr 10, 2026
3. github-actions

   added

   area-CodeGen-coreclrCLR JIT compiler in src/coreclr/src/jit and related components such as SuperPMICLR JIT compiler in src/coreclr/src/jit and related components such as SuperPMI

   on Apr 10, 2026
4. jakobbotsch

   added

   runtime-async

   and removed

   untriagedNew issue has not been triaged by the area ownerNew issue has not been triaged by the area owner

   on Apr 10, 2026
5. jakobbotsch

   added this to the 11.0.0 milestone on Apr 10, 2026
6. dotnet-policy-service commented on Apr 10, 2026

   

   dotnet-policy-serviceBot

   on Apr 10, 2026 – with Dotnet Policy Service

   Contributor

   More actions

   Tagging subscribers to this area: @JulieLeeMSFT, @jakobbotsch
   See info in area-owners.md if you want to be subscribed.
7. jakobbotsch

   added

   Priority:2Work that is important, but not critical for the releaseWork that is important, but not critical for the release

   on Jul 9, 2026
8. jakobbotsch

   added

   Priority:1Work that is critical for the release, but we could probably ship withoutWork that is critical for the release, but we could probably ship without

   and removed

   Priority:2Work that is important, but not critical for the releaseWork that is important, but not critical for the release

   on Jul 30, 2026
9. jakobbotsch commented on Aug 14, 2026

   

   jakobbotsch

   on Aug 14, 2026

   MemberAuthor

   More actions

   We introduce TLS access as part of the IR inserted to save contexts, and that means there will always be a GC safe point between the entry and the user's code. So I don't think there is a problem here in practice.

   I still think an explicit check is warranted in optRemoveRedundantZeroInits, but it can be done in .NET 12.
10. jakobbotsch

    modified the milestones: 11.0.0, 12.0.0 on Aug 14, 2026
11. jakobbotsch commented on Aug 14, 2026

    

    jakobbotsch

    on Aug 14, 2026

    MemberAuthor

    More actions

    Nope, I was able to produce an example repro that reports a garbage reference to the runtime using async versions. Moving it back...
12. jakobbotsch

    modified the milestones: 12.0.0, 11.0.0 on Aug 14, 2026
13. jakobbotsch

    closed this as completedin #132326on Aug 14, 2026
14. github-actions

    locked and limited conversation to collaborators on Sep 14, 2026