Sync all boost.context files with release 1.86.0 #20375
Open
+38
−24
Conversation
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
ndossche
reviewed
Nov 4, 2025
There was a problem hiding this comment.
Checked against upstream, looks like a valid sync.
Regarding the changes: this is mostly cleanup and one bugfix for s390x. That should likely be backported (or this PR should target a lower branch).
Why did you pick boost 1.86 though, there are newer versions?
|
Please target to what branch this is desired. I chose 1.86 as the current files are from somewhere 1.85-1.86. This PR is to sync the files with specific release tag, not to upgrade them to the latest version. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
While working on #19802 for boost.context I found out these 6 files to be out of sync with boost.context v1.86.0.
I have not much experience with these files and exotic platforms, please review this PR carefully.