Skip to content
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

backport #513 #520

Merged
merged 5 commits into from
Nov 30, 2024
Merged

backport #513 #520

merged 5 commits into from
Nov 30, 2024

Conversation

Freax13
Copy link
Member

@Freax13 Freax13 commented Nov 30, 2024

We need to backport #513 to v0.14 because there are a lot of people still depending on v0.14 and it's currently broken on nightly.

I created a new branch x86_64-0.14.x to use for backporting fixes. This branch currently points at the commit that released v0.14.12 (the last commit before we started merging v0.15 stuff into master). I enabled branch protections on this new branch. This PR targets that new branch.

The first commit in this PR adjusts CI to run on the new branch so that our CI pipeline can create the release.

For the second commit, I cherry-picked b9e3d25. This commit contains the fixes for newer nightlies. For the third commit, I cherry-picked 3fec974 to fix a deny-by-default warning. Note that this PR doesn't backport any other fixes.

The last two commits prepare a new release.

Note that this commit should not be merged into master. It's only
relevant for the x86_64-0.14.x branch.
This commit should not change the behavior of CI on the master branch.
A recent nightly changed the signature of Step::steps_between to match
the signature of Iterator::size_hint. This patch changes our
implementations to match the new signature.
@Freax13 Freax13 requested review from phil-opp and josephlr November 30, 2024 08:24
Starting with the latest nightly, this results in an error:

error: avoid using labels containing only the digits `0` and `1` in inline assembly
  --> src/instructions/segmentation.rs:81:18
   |
81 |                 "1:",
   |                  ^ use a different label that doesn't start with `0` or `1`
   |
   = note: an LLVM bug makes these labels ambiguous with a binary literal number
   = note: `#[deny(binary_asm_labels)]` on by default
Copy link
Member

@phil-opp phil-opp left a comment

Choose a reason for hiding this comment

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

Thank you!

@Freax13 Freax13 merged commit 1eb275b into x86_64-0.14.x Nov 30, 2024
7 of 12 checks passed
@Freax13 Freax13 deleted the backport/pr-513 branch November 30, 2024 09:12
@Freax13
Copy link
Member Author

Freax13 commented Nov 30, 2024

I had to update the allowed branches for the environment secret, but other than that it seems to have worked perfectly.

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.

2 participants