tests/debuginfo/macro-stepping.rs remains broken with SingleUseConsts
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 119k
- Forks
- 16.1k
- PR merge metrics
- PR metrics pending
Description
This is the part of @saethlin's #128945 that survived #130329. Reordering the IR in the front end in the SingleUseConsts pass breaks the stepping order. This could be mitigated to some extent (but not completely, unclear if it would be sufficient for this test to pass) with better support in LLVM for front ends to express which IR instructions should be considered for breakpoints.
@rustbot label +A-debuginfo +A-testsuite +A-llvm +A-mir +C-bug +T-compiler +WG-debugging +WG-llvm
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with tests/debuginfo/macro-stepping.rs and the SingleUseConsts pass, then review the related context in issues #128945 and #130329. Run the affected debuginfo test to reproduce the broken stepping order; done means the test passes with correct macro-stepping behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- compilers, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100