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.

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

Jump to bottom

Don't instrument tools when compiling with coverage #32848

Open
vedantk opened this issue Jun 18, 2017 · 2 comments
Open

Don't instrument tools when compiling with coverage #32848

vedantk opened this issue Jun 18, 2017 · 2 comments
Assignees
@vedantk
Labels
bugzilla Issues migrated from bugzilla cmake Build system in general and CMake in particular

Comments

@vedantk
Copy link
Collaborator

vedantk commented Jun 18, 2017

Bugzilla Link 33501
Version trunk
OS All

Extended Description

Tools like llvm-config, count, not, and FileCheck shouldn't be instrumented for coverage reporting. Doing so substantially slows down testing time, because large profiles for each binary need to be written out every time they are invoked.
@vedantk
Copy link
Collaborator Author

vedantk commented Jun 18, 2017

assigned to @vedantk

@vedantk
Copy link
Collaborator Author

vedantk commented Jun 18, 2017

(Note: the public coverage bot on GreenDragon works around the issue by copying in "fast" tools from the stage1 compiler after the coverage build is done. I don't have the numbers anymore, but as I recall this was a substantial speed win.)

@llvmbot llvmbot transferred this issue from llvm/llvm-bugzilla-archive Dec 10, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@vedantk vedantk

Labels
bugzilla Issues migrated from bugzilla cmake Build system in general and CMake in particular
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@vedantk