Conversation
This reverts commit 96a589a.
jjhelmus
added
platform:linux
|
Why are you running things like this with all Python versions and build variants? jw, seems unnecessary and want to understand if the subsetting is working |
Member
|
Merging assuming this is blocking release |
Contributor
Author
I wanted to ensure that reverting to GCC did not introduce new failures and fixed and fixed the current ones. The best method seemed to be to test everything that could be effected. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This reverts commit 96a589a.
Having a split LLVM / older GNU ld toolchain causes issues with relocation symbols and truncations.