Skip to content

Issues: rust-lang/rust

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.

Sign up for GitHub

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

Clear current search query, filters, and sorts
59 Open 258 Closed
59 Open 258 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

coverage: Restrict empty-span expansion to only cover { and } A-code-coverage Area: Source-based code coverage (-Cinstrument-coverage) S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#132675 opened Nov 6, 2024 by Zalathar Loading…
@jieyouxu
31
Tracking issue for release notes of #131829: Remove support for -Zprofile (gcov-style coverage instrumentation) A-code-coverage Area: Source-based code coverage (-Cinstrument-coverage) relnotes Marks issues that should be documented in the release notes of the next release. relnotes-tracking-issue Marks issues tracking what text to put in release notes. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#132447 opened Nov 1, 2024 by rustbot
1 of 3 tasks
1.84.0
1
Inlining -Cinstrument-coverage code into a uninstrumented crate causes problems A-code-coverage Area: Source-based code coverage (-Cinstrument-coverage) T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#132436 opened Nov 1, 2024 by Zalathar
Coverage information is wrong when using tracing A-code-coverage Area: Source-based code coverage (-Cinstrument-coverage) A-proc-macros Area: Procedural macros C-bug Category: This is a bug. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#131119 opened Oct 1, 2024 by xd009642
2
Stabilize #[coverage] attribute A-code-coverage Area: Source-based code coverage (-Cinstrument-coverage) 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. T-libs Relevant to the library team, which will review and decide on the PR/issue.
#130766 opened Sep 23, 2024 by clarfonthey Loading…
1
@Zalathar
39
coverage: Support match statements in branch coverage A-code-coverage Area: Source-based code coverage (-Cinstrument-coverage) 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.
#130744 opened Sep 23, 2024 by ranger-ross Loading…
@Zalathar
16
-C instrument-coverage misses regions in const assertions A-code-coverage Area: Source-based code coverage (-Cinstrument-coverage) C-bug Category: This is a bug. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#130502 opened Sep 18, 2024 by jfrimmel
1
[BUG] llvm-cov warning mismatched data when impl const fn A-code-coverage Area: Source-based code coverage (-Cinstrument-coverage) A-LLVM Area: Code generation parts specific to LLVM. Both correctness bugs and optimization-related issues. C-bug Category: This is a bug. S-has-mcve Status: A Minimal Complete and Verifiable Example has been found for this issue T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#130139 opened Sep 9, 2024 by loynoir
[BUG] llvm-cov warning mismatched data when triple slash safety comment above unsafe fn A-code-coverage Area: Source-based code coverage (-Cinstrument-coverage) A-LLVM Area: Code generation parts specific to LLVM. Both correctness bugs and optimization-related issues. C-bug Category: This is a bug. S-has-mcve Status: A Minimal Complete and Verifiable Example has been found for this issue T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#130097 opened Sep 8, 2024 by loynoir
[BUG] llvm-cov warning mismatched data when double slash comment above use A-code-coverage Area: Source-based code coverage (-Cinstrument-coverage) A-codegen Area: Code generation C-bug Category: This is a bug. requires-nightly This issue requires a nightly compiler in some way. S-has-mcve Status: A Minimal Complete and Verifiable Example has been found for this issue T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#130065 opened Sep 7, 2024 by loynoir
10
[Coverage][MCDC] Do not initialize mcdc parameters for instances containing no mcdc statements A-code-coverage Area: Source-based code coverage (-Cinstrument-coverage) 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.
#129989 opened Sep 5, 2024 by Lambdaris Loading…
@Zalathar
8
Coverage on stable 1.79.0 fails with : maybe try to call try_normalize_erasing_regions instead A-code-coverage Area: Source-based code coverage (-Cinstrument-coverage) C-bug Category: This is a bug. E-needs-mcve Call for participation: This issue has a repro, but needs a Minimal Complete and Verifiable Example I-ICE Issue: The compiler panicked, giving an Internal Compilation Error (ICE) ❄️ regression-from-stable-to-stable Performance or correctness regression from one stable version to another. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#125353 opened May 21, 2024 by la10736
11
Constant evaluation cannot have code coverage instrumentation A-code-coverage Area: Source-based code coverage (-Cinstrument-coverage) A-const-eval Area: Constant evaluation (MIR interpretation) C-enhancement Category: An issue proposing an enhancement or a PR with one. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#124732 opened May 5, 2024 by clarfonthey
9
-C instrument-coverage does not work with crate-type = ["dylib"] dependency on windows-msvc A-code-coverage Area: Source-based code coverage (-Cinstrument-coverage) C-bug Category: This is a bug. O-windows-msvc Toolchain: MSVC, Operating system: Windows
#124372 opened Apr 25, 2024 by taiki-e
2
Support mcdc analysis for pattern matching A-code-coverage Area: Source-based code coverage (-Cinstrument-coverage) S-blocked Status: Marked as blocked ❌ on something else such as an RFC or other implementation work. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#124278 opened Apr 23, 2024 by ZhuUx Loading…
@Zalathar
86
coverage: Treat each match arm as a "branch" for branch coverage A-code-coverage Area: Source-based code coverage (-Cinstrument-coverage) S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#124154 opened Apr 19, 2024 by Zalathar • Draft
26
Tracking implementation for MC/DC A-code-coverage Area: Source-based code coverage (-Cinstrument-coverage) C-tracking-issue Category: A tracking issue for an RFC or an unstable feature. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#124144 opened Apr 19, 2024 by ZhuUx
3 of 4 tasks
32
Known limitations of branch coverage instrumentation A-code-coverage Area: Source-based code coverage (-Cinstrument-coverage) T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#124118 opened Apr 18, 2024 by Zalathar
4 tasks
9
Coverage instrumentation loses information in macro-generated code A-code-coverage Area: Source-based code coverage (-Cinstrument-coverage) A-proc-macros Area: Procedural macros C-bug Category: This is a bug. E-needs-mcve Call for participation: This issue has a repro, but needs a Minimal Complete and Verifiable Example T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#123567 opened Apr 6, 2024 by narpfel
2
Codegen transformation of weak symbol to undefined across CGUs affects linking semantics A-code-coverage Area: Source-based code coverage (-Cinstrument-coverage) A-codegen Area: Code generation A-linkage Area: linking into static, shared libraries and binaries A-LTO Area: Link-time optimization (LTO) C-bug Category: This is a bug.
#120842 opened Feb 9, 2024 by zmodem
6
coverage: Don't show coverage for code paths that must panic/diverge A-code-coverage Area: Source-based code coverage (-Cinstrument-coverage) S-experimental Status: Ongoing experiment that does not require reviewing and won't be merged in its current state. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#120013 opened Jan 16, 2024 by Zalathar • Draft
12
Malformed coverage data when using llvm-cov A-code-coverage Area: Source-based code coverage (-Cinstrument-coverage) C-bug Category: This is a bug. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#119453 opened Dec 30, 2023 by StackOverflowExcept1on
16
invalid attempt to unwrap a None some_prev with -Cinstrument-coverage A-code-coverage Area: Source-based code coverage (-Cinstrument-coverage) C-bug Category: This is a bug. I-ICE Issue: The compiler panicked, giving an Internal Compilation Error (ICE) ❄️ T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#118662 opened Dec 6, 2023 by PalmPTSJ
5
"invalid attempt to unwrap a None some_prev" when using "-Cinstrument-coverage" A-code-coverage Area: Source-based code coverage (-Cinstrument-coverage) C-bug Category: This is a bug. I-ICE Issue: The compiler panicked, giving an Internal Compilation Error (ICE) ❄️ T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#118643 opened Dec 5, 2023 by Drakulix
11
Investigate why #113970 changes async2.rs coverage maps on some targets A-code-coverage Area: Source-based code coverage (-Cinstrument-coverage) T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
#116134 opened Sep 25, 2023 by Zalathar
9
ProTip! Adding no:label will show everything without a label.