Remove GTF_DEBUG_NODE_MORPHED. #6218

Activity

1. pgavlin

   self-assigned this

   on Jun 27, 2016
2. briansull

   changed the title [-]Remove `GTF_DEBUG_MORPHED`.[/-] [+]Remove `GTF_DEBUG_NODE_MORPHED`.[/+] on Jun 27, 2016
3. RussKeldorph

   unassigned

   pgavlin

   on Jan 13, 2018
4. msftgits

   transferred this issue fromdotnet/coreclron Jan 31, 2020
5. msftgits

   added this to the Future milestone on Jan 31, 2020
6. BruceForstall

   added

   JitUntriagedCLR JIT issues needing additional triageCLR JIT issues needing additional triage

   on Oct 28, 2020
7. AndyAyersMS commented on Oct 21, 2022

   

   AndyAyersMS

   on Oct 21, 2022

   Member

   More actions

   Seems like the main concern is not that we over morph but that we miss out on morphing something entirely. But I suppose in those cases where morphing actually does something required lack of morphing should become evident.
8. BruceForstall

   removed

   JitUntriagedCLR JIT issues needing additional triageCLR JIT issues needing additional triage

   on Jan 24, 2023
9. AndyAyersMS

   added a commit that references this issue on Dec 17, 2024

   JIT: revise how we track if nodes have been morphed

   ...

   This issue will close once commit 733c2a7 is merged into the 'main' branch.

   733c2a7
10. dotnet-policy-service

    added

    in-prThere is an active PR which will close this issue when it is mergedThere is an active PR which will close this issue when it is merged

    on Dec 17, 2024
11. AndyAyersMS

    closed this as completedin #110787on Dec 18, 2024
12. AndyAyersMS

    closed this as completedin 4822cc0on Dec 18, 2024
13. AndyAyersMS

    added a commit that references this issue on Dec 18, 2024

    JIT: revise how we track if nodes have been morphed (dotnet#110787)

    ...

    This issue will close once commit 4822cc0 is merged into the 'main' branch.

    4822cc0
14. github-actions

    locked and limited conversation to collaborators on Jan 18, 2025