-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add support for doubly nested intrinsic classes #105761
Conversation
cc @dotnet/jit-contrib PTAL @tannergooding @MichalStrehovsky @jkotas |
@@ -22,7 +22,9 @@ public static bool IsHardwareIntrinsic(MethodDesc method) | |||
if (owningType.IsIntrinsic && !owningType.HasInstantiation) | |||
{ | |||
var owningMdType = (MetadataType)owningType; | |||
string ns = owningMdType.ContainingType?.Namespace ?? owningMdType.Namespace; | |||
string ns = owningMdType.ContainingType?.ContainingType?.Namespace ?? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nit: It would be nice to avoid calling the virtual ContainingType
property multiple times.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks
System.Runtime.Intrinsics.X86.Avx10v1+V512+X64.IsSupported
currently results in an infinite loop. This PR fixes the problem by adding support in various places for hardware intrinsic classes nested more than once.getMethodNameFromMetadata
to allow returning names of multiple enclosing classesAvx10v1
supportFix #105402