public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug gcov-profile/98739] -fprofile-reproducible is broken Date: Mon, 25 Jan 2021 12:31:32 +0000 [thread overview] Message-ID: <bug-98739-4-pcEOehSR8M@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-98739-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98739 --- Comment #4 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Martin Liska <marxin@gcc.gnu.org>: https://gcc.gnu.org/g:5089df534b85b795bfcdca8f4f1957ad15a60558 commit r11-6891-g5089df534b85b795bfcdca8f4f1957ad15a60558 Author: Martin Liska <mliska@suse.cz> Date: Fri Jan 22 11:27:16 2021 +0100 Restore profile reproducibility. gcc/ChangeLog: PR gcov-profile/98739 * common.opt: Add missing sign symbol. * value-prof.c (get_nth_most_common_value): Restore handling of PROFILE_REPRODUCIBILITY_PARALLEL_RUNS and PROFILE_REPRODUCIBILITY_MULTITHREADED. libgcc/ChangeLog: PR gcov-profile/98739 * libgcov-merge.c (__gcov_merge_topn): Mark when merging ends with a dropped counter. * libgcov.h (gcov_topn_add_value): Add return value.
next prev parent reply other threads:[~2021-01-25 12:31 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-01-18 23:24 [Bug gcov-profile/98739] New: " hubicka at gcc dot gnu.org 2021-01-19 7:59 ` [Bug gcov-profile/98739] " rguenth at gcc dot gnu.org 2021-01-19 9:18 ` marxin at gcc dot gnu.org 2021-01-19 9:18 ` marxin at gcc dot gnu.org 2021-01-22 13:21 ` cvs-commit at gcc dot gnu.org 2021-01-25 12:31 ` cvs-commit at gcc dot gnu.org [this message] 2021-01-25 12:31 ` cvs-commit at gcc dot gnu.org 2021-01-26 11:47 ` cvs-commit at gcc dot gnu.org 2021-01-26 11:50 ` cvs-commit at gcc dot gnu.org 2021-01-26 11:50 ` marxin at gcc dot gnu.org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-98739-4-pcEOehSR8M@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).