Skip to content

base-builder: introspector: disable dead code optimizations #13315

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

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

DavidKorczynski
Copy link
Collaborator

Despite -O0 these optimizations still happen. This is particularly important for OFG runs where we run on new projects as they will be based on an empty fuzzing harness, meaning a lot of the code is potentially affected. Less so on existing projects where the optimizations are less impactful.

Despite -O0 these optimizations still happen. This is particularly important for OFG runs where we run on new projects as they will be based on an empty fuzzing harness, meaning a lot of the code is potentially affected. Less so on existing projects where the optimizations are less impactful.
@DavidKorczynski
Copy link
Collaborator Author

/gcbrun trial_build.py all --sanitizer introspector --fuzzing-engine libfuzzer

@@ -82,7 +82,7 @@ ENV SANITIZER_FLAGS_memory "-fsanitize=memory -fsanitize-memory-track-origins"

ENV SANITIZER_FLAGS_thread "-fsanitize=thread"

ENV SANITIZER_FLAGS_introspector "-O0 -flto -fno-inline-functions -fuse-ld=gold -Wno-unused-command-line-argument"
ENV SANITIZER_FLAGS_introspector "-O0 -flto -fno-inline-functions -fuse-ld=gold -Wno-unused-command-line-argument -Wl,--mllvm,-compute-dead=false -disable-globaldce"
Copy link
Collaborator

Choose a reason for hiding this comment

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

are there any implications on speed or resulting database size?

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