Skip to content

Implement DLQ_GetPtrAuthMask using info from debugserver. … #4110

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

Merged
merged 1 commit into from
Mar 24, 2022

Conversation

adrian-prantl
Copy link

rdar://90718091

@JDevlieghere
Copy link

JDevlieghere commented Mar 23, 2022

I assume you're planning to land the generic part of this upstream? If so it might be nice to split this into 2 commits and then cherrypick the one to llvm.org once it's merged here.

@adrian-prantl adrian-prantl force-pushed the 90718091 branch 2 times, most recently from 49a0063 to 23fa012 Compare March 23, 2022 20:01
@adrian-prantl
Copy link
Author

@swift-ci test

@adrian-prantl
Copy link
Author

adrian-prantl added a commit to llvm/llvm-project that referenced this pull request Mar 23, 2022
This is needed by the Swift Plugin.

See also  swiftlang#4110.

Differential Revision: https://reviews.llvm.org/D122347
@adrian-prantl
Copy link
Author

@swift-ci test

return false;
case DLQ_GetPtrAuthMask: {
assert(m_process.GetCodeAddressMask() == m_process.GetDataAddressMask() &&
"not supported");

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nit: different code and address masks are not supported?

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does this code know if the mask returned is used for data or for code addresses? Linux standardized on the code/data masks, but I don't think the distinction is possible in AArch64, I'm not sure what target motivated that choice. I think a sanity check of ensuring that they're the same, if we don't know what this mask might be used for, is correct.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The swift::reflection::MemoryReader API doesn't distinguish between the two.

@JDevlieghere
Copy link

@swift-ci please test macos

@adrian-prantl adrian-prantl merged commit 2b47160 into swiftlang:stable/20211026 Mar 24, 2022
mem-frob pushed a commit to draperlaboratory/hope-llvm-project that referenced this pull request Oct 7, 2022
This is needed by the Swift Plugin.

See also  swiftlang/llvm-project#4110.

Differential Revision: https://reviews.llvm.org/D122347
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants