Skip to content

Investigate potential ARM64 perf improvements in AsciiUtility and Utf16Utility #40805

Closed

Description

@pgovind

This is a follow up to #39506, #39507 and #39050 to investigate Tamar's suggestions for improving ARM64 perf in ASCIIUtility and Utf16Utility. The suggestions are #39506 (comment), #39507 (comment) and #39507 (comment)

cc @carlossanlop @jeffhandley @kunalspathak @echesakovMSFT @tannergooding

Activity

  1. added this to the Future milestone on Aug 13, 2020
  2. removed
    untriagedNew issue has not been triaged by the area owner
    on Aug 13, 2020
  3. dotnet-policy-service commented on Feb 18, 2025

    @dotnet-policy-service
    Contributor

    Due to lack of recent activity, this issue has been marked as a candidate for backlog cleanup. It will be closed if no further activity occurs within 14 more days. Any new comment (by anyone, not necessarily the author) will undo this process.

    This process is part of our issue cleanup automation.

  4. dotnet-policy-service commented on Mar 4, 2025

    @dotnet-policy-service
    Contributor

    This issue will now be closed since it had been marked no-recent-activity but received no further activity in the past 14 days. It is still possible to reopen or comment on the issue, but please note that the issue will be locked if it remains inactive for another 30 days.

  5. removed this from the Future milestone on Mar 4, 2025
  6. locked and limited conversation to collaborators on Apr 4, 2025
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

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions