Skip to content

Conversation

tshepang
Copy link
Member

@tshepang tshepang commented Jun 30, 2025

Added this since the other label operand tests are only for x86

@rustbot
Copy link
Collaborator

rustbot commented Jun 30, 2025

r? @lcnr

rustbot has assigned @lcnr.
They will have a look at your PR within the next two weeks and either review your PR or reassign to another reviewer.

Use r? to explicitly pick a reviewer

@rustbot rustbot added S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. labels Jun 30, 2025
@lcnr
Copy link
Contributor

lcnr commented Jun 30, 2025

don't know how label works

r? @Amanieu maybe

@rustbot rustbot assigned Amanieu and unassigned lcnr Jun 30, 2025
@@ -0,0 +1,47 @@
//@ run-pass
//@ needs-asm-support
Copy link
Member

Choose a reason for hiding this comment

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

This is going to fail on targets that aren't x86, arm or risc-v. Either add a fallback or split this into separate tests that are only enabled for that particular architecture.

bors-ferrocene bot added a commit to ferrocene/ferrocene that referenced this pull request Aug 7, 2025
1633: [1.88] add test: inline assembly label operand r=Hoverbear a=tshepang

Backports rust-lang/rust#143227 as we need it for satisfying traceability matrix.

Co-authored-by: Tshepang Mbambo <hopsi@tuta.io>
@apiraino
Copy link
Contributor

Switching to waiting on author due to this comment. Feel free to request a review with @rustbot ready, thanks!

@rustbot author

@rustbot rustbot added S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. and removed S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels Aug 28, 2025
@Dylan-DPC
Copy link
Member

@tshepang any updates on this? thanks

@tshepang
Copy link
Member Author

let me do this within a week

Hoverbear added a commit to ferrocene/ferrocene that referenced this pull request Oct 3, 2025
Hoverbear added a commit to ferrocene/ferrocene that referenced this pull request Oct 3, 2025
Hoverbear added a commit to ferrocene/ferrocene that referenced this pull request Oct 3, 2025
Others in the file skip the module name
@rustbot
Copy link
Collaborator

rustbot commented Oct 4, 2025

Some changes occurred in src/tools/compiletest

cc @jieyouxu

@rustbot
Copy link
Collaborator

rustbot commented Oct 4, 2025

This PR was rebased onto a different master commit. Here's a range-diff highlighting what actually changed.

Rebasing is a normal part of keeping PRs up to date, so no action is needed—this note is just to help reviewers.

@tshepang
Copy link
Member Author

tshepang commented Oct 4, 2025

@rustbot ready

@rustbot rustbot added S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. and removed S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. labels Oct 4, 2025
}

// fallback
#[cfg(other)]
Copy link
Member

Choose a reason for hiding this comment

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

This isn't needed any more, just don't execute any revision at all if none of the needs-* predicates match.

Copy link
Member Author

Choose a reason for hiding this comment

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

would this mean the test will fail if another arch gets support for inline assembly

Copy link
Member

Choose a reason for hiding this comment

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

If you just remove other from the list of revisions at the top of the file then this test simply won't execute for any architectures other than the ones listed.

Copy link
Member Author

Choose a reason for hiding this comment

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

oh, that I did not expect... thought other archs would still run main and fail due to missing fn make_true

@rustbot rustbot added the A-compiletest Area: The compiletest test runner label Oct 7, 2025
@rustbot rustbot added A-testsuite Area: The testsuite used to check the correctness of rustc T-bootstrap Relevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap) labels Oct 7, 2025
@tshepang
Copy link
Member Author

tshepang commented Oct 7, 2025

@bors ready

@Amanieu
Copy link
Member

Amanieu commented Oct 8, 2025

@bors r+

@bors
Copy link
Collaborator

bors commented Oct 8, 2025

📌 Commit c7d180c has been approved by Amanieu

It is now in the queue for this repository.

@bors bors added S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. and removed S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels Oct 8, 2025
@bors
Copy link
Collaborator

bors commented Oct 9, 2025

⌛ Testing commit c7d180c with merge bd34871...

@bors
Copy link
Collaborator

bors commented Oct 9, 2025

☀️ Test successful - checks-actions
Approved by: Amanieu
Pushing bd34871 to master...

@bors bors added the merged-by-bors This PR was explicitly merged by bors. label Oct 9, 2025
@bors bors merged commit bd34871 into rust-lang:master Oct 9, 2025
11 checks passed
@rustbot rustbot added this to the 1.92.0 milestone Oct 9, 2025
Copy link
Contributor

github-actions bot commented Oct 9, 2025

What is this? This is an experimental post-merge analysis report that shows differences in test outcomes between the merged PR and its parent PR.

Comparing 61efd19 (parent) -> bd34871 (this PR)

Test differences

Show 20 test diffs

Stage 1

  • [ui] tests/ui/asm/label-operand.rs#aarch64: [missing] -> ignore (only executed when the architecture is aarch64) (J4)
  • [ui] tests/ui/asm/label-operand.rs#arm: [missing] -> ignore (only executed when the architecture is arm) (J4)
  • [ui] tests/ui/asm/label-operand.rs#arm64ec: [missing] -> ignore (only executed when the architecture is arm64ec) (J4)
  • [ui] tests/ui/asm/label-operand.rs#riscv32: [missing] -> ignore (only executed when the architecture is riscv32) (J4)
  • [ui] tests/ui/asm/label-operand.rs#riscv64: [missing] -> ignore (only executed when the architecture is riscv64) (J4)
  • [ui] tests/ui/asm/label-operand.rs#x86: [missing] -> ignore (only executed when the architecture is x86) (J4)
  • [ui] tests/ui/asm/label-operand.rs#x86_64: [missing] -> pass (J4)

Stage 2

  • [ui] tests/ui/asm/label-operand.rs#aarch64: [missing] -> pass (J0)
  • [ui] tests/ui/asm/label-operand.rs#aarch64: [missing] -> ignore (only executed when the architecture is aarch64) (J1)
  • [ui] tests/ui/asm/label-operand.rs#x86: [missing] -> ignore (only executed when the architecture is x86) (J2)
  • [ui] tests/ui/asm/label-operand.rs#arm: [missing] -> ignore (only executed when the architecture is arm) (J3)
  • [ui] tests/ui/asm/label-operand.rs#arm64ec: [missing] -> ignore (only executed when the architecture is arm64ec) (J5)
  • [ui] tests/ui/asm/label-operand.rs#riscv32: [missing] -> ignore (only executed when the architecture is riscv32) (J5)
  • [ui] tests/ui/asm/label-operand.rs#riscv64: [missing] -> ignore (only executed when the architecture is riscv64) (J5)
  • [ui] tests/ui/asm/label-operand.rs#x86_64: [missing] -> pass (J6)
  • [ui] tests/ui/asm/label-operand.rs#arm: [missing] -> pass (J7)
  • [ui] tests/ui/asm/label-operand.rs#x86: [missing] -> pass (J8)
  • [ui] tests/ui/asm/label-operand.rs#x86_64: [missing] -> ignore (only executed when the architecture is x86_64) (J9)

Additionally, 2 doctest diffs were found. These are ignored, as they are noisy.

Job group index

Test dashboard

Run

cargo run --manifest-path src/ci/citool/Cargo.toml -- \
    test-dashboard bd3487101ff9397ca8a54dd83aa360d93342b82e --output-dir test-dashboard

And then open test-dashboard/index.html in your browser to see an overview of all executed tests.

Job duration changes

  1. dist-x86_64-apple: 6220.4s -> 7487.4s (20.4%)
  2. aarch64-gnu-llvm-20-1: 3295.2s -> 3820.9s (16.0%)
  3. aarch64-msvc-2: 4796.9s -> 5466.3s (14.0%)
  4. aarch64-gnu-llvm-20-2: 2190.8s -> 2462.2s (12.4%)
  5. dist-aarch64-msvc: 7188.1s -> 6345.8s (-11.7%)
  6. x86_64-gnu-tools: 3266.2s -> 3642.7s (11.5%)
  7. dist-apple-various: 4798.1s -> 4246.5s (-11.5%)
  8. x86_64-gnu-miri: 4338.6s -> 4815.4s (11.0%)
  9. dist-x86_64-windows-gnullvm: 4763.4s -> 5281.0s (10.9%)
  10. x86_64-gnu-llvm-20: 2441.1s -> 2699.0s (10.6%)
How to interpret the job duration changes?

Job durations can vary a lot, based on the actual runner instance
that executed the job, system noise, invalidated caches, etc. The table above is provided
mostly for t-infra members, for simpler debugging of potential CI slow-downs.

@tshepang tshepang deleted the asm-label-operand branch October 9, 2025 05:48
@rust-timer
Copy link
Collaborator

Finished benchmarking commit (bd34871): comparison URL.

Overall result: no relevant changes - no action needed

@rustbot label: -perf-regression

Instruction count

This benchmark run did not return any relevant results for this metric.

Max RSS (memory usage)

Results (primary -1.5%)

A less reliable metric. May be of interest, but not used to determine the overall result above.

mean range count
Regressions ❌
(primary)
1.3% [1.3%, 1.3%] 1
Regressions ❌
(secondary)
- - 0
Improvements ✅
(primary)
-4.2% [-4.2%, -4.2%] 1
Improvements ✅
(secondary)
- - 0
All ❌✅ (primary) -1.5% [-4.2%, 1.3%] 2

Cycles

Results (secondary -2.0%)

A less reliable metric. May be of interest, but not used to determine the overall result above.

mean range count
Regressions ❌
(primary)
- - 0
Regressions ❌
(secondary)
- - 0
Improvements ✅
(primary)
- - 0
Improvements ✅
(secondary)
-2.0% [-2.0%, -2.0%] 1
All ❌✅ (primary) - - 0

Binary size

This benchmark run did not return any relevant results for this metric.

Bootstrap: 473.034s -> 474.495s (0.31%)
Artifact size: 388.41 MiB -> 388.40 MiB (-0.00%)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

A-compiletest Area: The compiletest test runner A-testsuite Area: The testsuite used to check the correctness of rustc merged-by-bors This PR was explicitly merged by bors. S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. T-bootstrap Relevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap) T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

8 participants