Repository navigation
Test #[track_caller] in async on gcc backend - #163262
Merged
rust-bors[bot] merged 1 commit intoOct 19, 2026
Merged
Conversation
rustbot
added
S-waiting-on-author
theemathas
marked this pull request as ready for review
September 24, 2026 15:04
rustbot
added
the
S-waiting-on-review
Collaborator
|
cc @rust-lang/miri |
rustbot
removed
the
S-waiting-on-author
Collaborator
|
r? @davidtwco rustbot has assigned @davidtwco. Use Why was this reviewer chosen?The reviewer was selected based on:
|
RalfJung
reviewed
Sep 25, 2026
theemathas
force-pushed
the
async-panic-track-caller-gcc-tests
branch
2 times, most recently
from
September 27, 2026 09:41
657d87c to
4f8c49f
Compare
This comment has been minimized.
This comment has been minimized.
theemathas
force-pushed
the
async-panic-track-caller-gcc-tests
branch
from
October 1, 2026 12:36
4f8c49f to
b7503bd
Compare
This comment has been minimized.
This comment has been minimized.
theemathas
force-pushed
the
async-panic-track-caller-gcc-tests
branch
from
October 2, 2026 15:02
b7503bd to
7631728
Compare
This comment has been minimized.
This comment has been minimized.
Contributor
Author
|
@rustbot reroll |
Previously, in rust-lang#161972, this test was skipped on gcc, due to a bug in rustc_codegen_gcc. The bug was fixed by the subtree update at rust-lang#162499.
theemathas
force-pushed
the
async-panic-track-caller-gcc-tests
branch
from
October 19, 2026 02:21
7631728 to
236daa7
Compare
Collaborator
|
This PR was rebased onto a different main 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. |
Member
|
@GuillaumeGomez or @antoyo would probably be the most suited reviewer here. |
GuillaumeGomez
approved these changes
Oct 19, 2026
Member
|
If test is passing, I think it's safe to assume it works. @bors r+ rollup |
Contributor
rust-bors
Bot
added
S-waiting-on-bors
rust-bors Bot
pushed a commit
that referenced
this pull request
Oct 19, 2026
…uwer Rollup of 5 pull requests Successful merges: - #164562 (`rust-analyzer` subtree update) - #164369 (Make tuple `PartialOrd` chaining easier on mir-opt) - #163262 (Test `#[track_caller]` in async on gcc backend) - #164346 (avoid exporting non-instantiable mono items) - #164505 (Re-enable parallelism for coroutine_by_move_body_def_id)
WhySoBad
pushed a commit
to WhySoBad/miri
that referenced
this pull request
Oct 20, 2026
…uwer Rollup of 5 pull requests Successful merges: - rust-lang/rust#164562 (`rust-analyzer` subtree update) - rust-lang/rust#164369 (Make tuple `PartialOrd` chaining easier on mir-opt) - rust-lang/rust#163262 (Test `#[track_caller]` in async on gcc backend) - rust-lang/rust#164346 (avoid exporting non-instantiable mono items) - rust-lang/rust#164505 (Re-enable parallelism for coroutine_by_move_body_def_id)
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
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.
Previously, in #161972, this test was skipped on gcc, due to a bug in
rustc_codegen_gcc. The bug was fixed by the subtree update at #162499.