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.

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

Build proper release binaries by default #139

Merged
merged 1 commit into from Nov 27, 2020
Merged

Conversation

bmwiedemann
Copy link
Contributor

Build proper release binaries by default
Because -fprofile-arcs introduces non-determinism via
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96970
and release binaries should not be instrumented like this anyway.

This change makes life easier for distribution packagers.

This PR was done while working on reproducible builds for openSUSE.

Because -fprofile-arcs causes non-determinism via
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96970
and release binaries should not be instrumented like this anyway.

This PR was done while working on reproducible builds for openSUSE.
@codecov
Copy link

codecov bot commented Sep 8, 2020

Codecov Report

Merging #139 into master will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##           master     #139   +/-   ##
=======================================
  Coverage   84.94%   84.94%           
=======================================
  Files          36       36           
  Lines        3307     3307           
=======================================
  Hits         2809     2809           
  Misses        498      498           

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 6f4f25e...60a9ec1. Read the comment docs.

@hoene hoene merged commit 590776d into hoene:master Nov 27, 2020
2 checks passed
@bmwiedemann bmwiedemann deleted the coverage branch February 11, 2021 08:55
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.

None yet

2 participants