Skip to content

Crossgen2 work for .NET 8 #85736

Closed
Closed

Description

@trylek

Real bugs and deficiencies

Static virtual methods

Possible future work

Nice to have

Individual test bugs

/cc @dotnet/crossgen-contrib

Activity

  1. added this to the 8.0.0 milestone on May 3, 2023
  2. changed the title [-][WIP] Crossgen2 work for .NET 8[/-] [+]Crossgen2 work for .NET 8[/+] on May 3, 2023
  3. trylek commented on May 4, 2023

    @trylek
    MemberAuthor

    I have made two small fixes to the list - yesterday I missed the generic cycle bug as the open issue has somewhat cryptic title, I have also fixed the link to Mark's PR fixing type initialization ordering, yesterday I pasted the wrong link to a related issue. For commenting on individual issues feel free to use the original issue threads, my expectation is that this issue is only going to be used to prioritize and drive fixing the issues and to track progress of that effort (and possible overflow work to .NET 9 as not all above bullet points are critical for .NET 8 and, as you can see, there's just a lot of stuff).

  4. trylek commented on Aug 1, 2023

    @trylek
    MemberAuthor

    As this is just an overarching issue summarizing Crossgen2 work and we're close to wrapping up .NET 8, I'm closing this issue for now; I assume that as part of .NET 9 planning we'll consider picking up some of the remaining work for .NET 9.

  5. ghost locked as resolved and limited conversation to collaborators on Sep 1, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions