Skip to content

Conversation

@bulbazord
Copy link

Both llvm-project and swift have changed upstream, so we need to adjust accordingly.

cc @JDevlieghere @dcci

This changed in commit f6643af in the swift
project.
This appeared to be removed in commit 27df2d9,
so most likely this was the result of a mismerge
Commit c9a39a8 modified the constructor.
I'm not entirely sure what name we should be giving here, but this code isn't in
llvm.org so I gave it something I thought would be reflective of the intention.
…operties

GetGlobalModuleListProperties() returns a ModuleListProperties, but that class
has an implicitly deleted copy constructor. Therefore we should be grabbing a
reference to the ModuleListProperties. Additionally, the uses I noticed in
SwiftASTContext can be made const.
@JDevlieghere JDevlieghere merged commit aa90800 into swiftlang:swift/master-next Jan 22, 2020
@varungandhi-apple
Copy link

I think this change is ok (because the default SILOptions has verbose = false), but is there a reason you wrote different code here instead of cherry-picking the LLDB change in #609 for the first commit?

@bulbazord bulbazord deleted the fix-swift-master-next branch January 23, 2020 00:20
@bulbazord
Copy link
Author

@varungandhi-apple: No reason other than I didn't look into it.

@varungandhi-apple
Copy link

Thanks for the fix anyways! :)

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.

3 participants