You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Ah thanks for pointing this out! I had seen this in a build log once but never got around to actually figuring out why this was happening. Adding the new libraries to the list seems fine if that's what's needed.
Is there a broader issue tracking this in general? I'm unfamiliar with this issue, but this list feels like a workaround rather than a solution and we should make sure that we have something tracking an actual solution unless we've decided that this list is the way to do that
Is there a broader issue tracking this in general?
Other than the original issue reporting excessive memory use when linking because of this, swiftlang/swift#58380, not that I can find.
this list feels like a workaround rather than a solution and we should make sure that we have something tracking an actual solution unless we've decided that this list is the way to do that
Based on the discussion in that pull adding Foundation to the list, it appears the list is considered a hack just to fix the memory issue for now.
Perhaps the real solution would be to place those linker flags in a set, so there is no duplication of any autolinked libraries. If you'd like to take that up instead, go for it.
The Swift compiler maintains an array of Swift runtime libraries to cache and not repeat when linking, to which Foundation was added a couple years ago, swiftlang/swift#64312. Now that these two new libraries were added, they should be added to that array too, else the Swift compiler does this on the Swift 6.0 linux CI:
It's not as bad in 6.1 trunk for some reason, but they're still repeated.
The text was updated successfully, but these errors were encountered: