-
Notifications
You must be signed in to change notification settings - Fork 5k
Minor changes to make it easier to sync diagnostic repo copy #107066
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
Conversation
Tagging subscribers to this area: @mangod9 |
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.
Lgtm. A GC / VM dev should also ok this.
@@ -2093,7 +2095,7 @@ void GcInfoDecoder::ReportRegisterToGC( | |||
LOG((LF_GCROOTS, LL_INFO1000, "Reporting " FMT_REG, regNum )); | |||
|
|||
OBJECTREF* pObjRef = GetRegisterSlot( regNum, pRD ); | |||
#if defined(TARGET_UNIX) && !defined(FEATURE_NATIVEAOT) && !defined(SOS_TARGET_AMD64) | |||
#if defined(TARGET_UNIX) && !defined(FEATURE_NATIVEAOT) && !defined(SOS_TARGET_RISCV64) |
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.
Was replacing ARM64 with RISCV64 intentional or do we need both?
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.
Yes, they were incorrect and caused build problems in the diagnostic repo. This section of code is under ifdef TARGET_RISCV64.
@@ -1976,7 +1978,7 @@ void GcInfoDecoder::ReportRegisterToGC( | |||
|
|||
gcFlags |= GC_CALL_PINNED; | |||
} | |||
#endif // TARGET_UNIX && !SOS_TARGET_ARM64 | |||
#endif // TARGET_UNIX && !SOS_TARGET_LOONGARCH64 |
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.
Also here, should we keep both conditions?
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.
Yes, they were incorrect and caused build problems in the diagnostic repo. This section of code is under ifdef TARGET_LOONGARCH64.
…107066) * Minor changes to make it easier to sync diagnostic repo copy * Undo ELF.h changes.
No description provided.