Skip to content

[Dexter] Remove clang-opt-bisect analyzer tool #128165

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.

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

Merged
merged 1 commit into from
Feb 24, 2025

Conversation

jmorse
Copy link
Member

@jmorse jmorse commented Feb 21, 2025

The idea behind this tool was that you'd instrument a source file to measure its debug-info quality, then watch as it progressively got worse with more optimisations being enabled in clang. However we've since stripped the "building" portions of Dexter out as they were ill placed, which makes this tooling redundant. The lack of init.py adjacent to it means it couldn't be run anyway.

The core idea behind this is still sound; just it's best placed on the other side of the build system, something that Dexter shouldn't try to solve.

The idea behind this tool was that you'd instrument a source file to
measure its debug-info quality, then watch as it progressively got worse
with more optimisations being enabled in clang. However we've since
stripped the "building" portions of Dexter out as they were ill placed,
which makes this tooling redundant. The lack of __init__.py adjacent to it
means it couldn't be run anyway.

The core idea behind this is still sound; just it's best placed on the
other side of the build system, something that Dexter shouldn't try to
solve.
Copy link
Contributor

@SLTozer SLTozer left a comment

Choose a reason for hiding this comment

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

Thought we'd removed this already! There are no other lingering references to the tool or tests that depend on it AFAICT, so fully removing this file should be fine.

@jmorse jmorse merged commit 1ed359e into llvm:main Feb 24, 2025
10 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants