You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Fixes#99214 by handling GT_SWIFT_ERROR in Compiler::gtCloneExpr.
cc @jakobbotsch. Since this isn't the first time an outerloop pipeline has failed due to a missing GT_SWIFT_ERROR switch case, I tried to look for other missing cases by searching for similarly-handled GenTree nodes. It's not the most precise method, but I did notice we aren't explicitly handling GT_SWIFT_ERROR in GenTree::Compare -- we return false if we encounter it. Just to check, is this the correct behavior, since GT_SWIFT_ERROR represents a value unknown at compile time?
Fixes #99214 by handling GT_SWIFT_ERROR in Compiler::gtCloneExpr.
cc @jakobbotsch. Since this isn't the first time an outerloop pipeline has failed due to a missing GT_SWIFT_ERROR switch case, I tried to look for other missing cases by searching for similarly-handled GenTree nodes. It's not the most precise method, but I did notice we aren't explicitly handling GT_SWIFT_ERROR in GenTree::Compare -- we return false if we encounter it. Just to check, is this the correct behavior, since GT_SWIFT_ERROR represents a value unknown at compile time?
Fixes #99214 by handling GT_SWIFT_ERROR in Compiler::gtCloneExpr.
cc @jakobbotsch. Since this isn't the first time an outerloop pipeline has failed due to a missing GT_SWIFT_ERROR switch case, I tried to look for other missing cases by searching for similarly-handled GenTree nodes. It's not the most precise method, but I did notice we aren't explicitly handling GT_SWIFT_ERROR in GenTree::Compare -- we return false if we encounter it. Just to check, is this the correct behavior, since GT_SWIFT_ERROR represents a value unknown at compile time?
GenTree::Compare can return true for it. It is a syntactic check -- it also returns true for two syntactically equal calls or indirections even though those can return different values.
GenTree::Compare can return true for it. It is a syntactic check -- it also returns true for two syntactically equal calls or indirections even though those can return different values.
I see, thanks for letting me know -- I'll update it separately.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
area-CodeGen-coreclrCLR JIT compiler in src/coreclr/src/jit and related components such as SuperPMI
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #99214 by handling
GT_SWIFT_ERRORinCompiler::gtCloneExpr.cc @jakobbotsch. Since this isn't the first time an outerloop pipeline has failed due to a missing
GT_SWIFT_ERRORswitch case, I tried to look for other missing cases by searching for similarly-handledGenTreenodes. It's not the most precise method, but I did notice we aren't explicitly handlingGT_SWIFT_ERRORinGenTree::Compare-- we return false if we encounter it. Just to check, is this the correct behavior, sinceGT_SWIFT_ERRORrepresents a value unknown at compile time?