Skip to content

[20250402][LLDB] Fix build errors #10599

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 20 commits into from
May 2, 2025

Conversation

AnthonyLatsis
Copy link

No description provided.

@@ -1269,7 +1269,7 @@ TypeSystemSwiftTypeRef::Canonicalize(swift::Demangle::Demangler &dem,
if (node->getKind() != Node::Kind::BoundGenericTypeAlias &&
node->getKind() != Node::Kind::TypeAlias)
// Resolve any type aliases in the resolved type.
return GetCanonicalNode(dem, node);
return GetCanonicalNode(dem, node, flavor);

Choose a reason for hiding this comment

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

This change surprises me. @augusto2112 Were we missing a cherry-pick on next?

Copy link
Author

Choose a reason for hiding this comment

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

Cannot find one. This line was added in 6c485cd.

Copy link
Author

@AnthonyLatsis AnthonyLatsis May 1, 2025

Choose a reason for hiding this comment

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

So the flavor thing landed on next and this code was cherry-picked from the old stable branch to next after that and presumably not tested for Swift.

Copy link

Choose a reason for hiding this comment

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

If I'm following commits through properly, this was #9883 on swift/release/6.1. There's a merge of that to stable/20240723 in d53ecfc (not sure the PR for this one though). And also cherry-picked to next in #9913, but the next cherry-pick didn't fix up the GetCanonicalNode call.

TLDR: I think everything that needs to be cherry-picked, is, and this is just a fix-up that wasn't made on next.

@@ -2905,8 +2905,7 @@ std::optional<SwiftNominalType> GetSwiftClass(ValueObject &valobj,

auto isa_load_addr = descriptor_sp->GetISA();
Address isa;
const auto &sections = objc_runtime.GetTargetRef().GetSectionLoadList();
if (!sections.ResolveLoadAddress(isa_load_addr, isa))
if (!objc_runtime.GetTargetRef().ResolveLoadAddress(isa_load_addr, isa))

Choose a reason for hiding this comment

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

Is this forwarding the call to the SectionLoadList?

Copy link
Author

Choose a reason for hiding this comment

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

Yes.

adrian-prantl and others added 16 commits May 1, 2025 19:05
…e to return llvm::Expected (llvm#129601)"

This patch pushes the error handling boundary for the GetBitSize()
methods from Runtime into the Type and CompilerType APIs. This makes
it easier to diagnose problems thanks to more meaningful error
messages being available. GetBitSize() is often the first thing LLDB
asks about a type, so this method is particularly important for a
better user experience.

rdar://145667239
(cherry picked from commit 878a64f)

(cherry picked from commit 642dcd7)
We lost a conditionally used variable in
15070b3.
We accidentally redefined a function in
305e024.
@AnthonyLatsis
Copy link
Author

@swift-ci please test

@adrian-prantl adrian-prantl merged commit 9aad9fb into swiftlang:stable/20250402 May 2, 2025
0 of 3 checks passed
@AnthonyLatsis AnthonyLatsis deleted the rebranch-fixes branch May 3, 2025 17:19
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.

5 participants