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/97193] [9/10 Regression] .gcno files are not written to same directory as the object file Date: Fri, 02 Oct 2020 11:16:54 +0000 [thread overview] Message-ID: <bug-97193-4-jfhBhoY7tl@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-97193-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97193 --- Comment #7 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-10 branch has been updated by Martin Liska <marxin@gcc.gnu.org>: https://gcc.gnu.org/g:f97ef0b2dfdad07db3d564b932c7b7373654b7d4 commit r10-8843-gf97ef0b2dfdad07db3d564b932c7b7373654b7d4 Author: Martin Liska <mliska@suse.cz> Date: Fri Sep 25 10:53:26 2020 +0200 GCOV: do not mangle .gcno files. gcc/ChangeLog: PR gcov-profile/97193 * coverage.c (coverage_init): GCDA note files should not be mangled and should end in output directory. (cherry picked from commit f8dcbea5d2fb17dca3a7de97f15fc49997222365)
next prev parent reply other threads:[~2020-10-02 11:16 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-09-24 12:22 [Bug gcov-profile/97193] New: " mario at klebsch dot de 2020-09-24 12:51 ` [Bug gcov-profile/97193] " rguenth at gcc dot gnu.org 2020-09-24 12:57 ` marxin at gcc dot gnu.org 2020-09-24 20:27 ` mario at klebsch dot de 2020-09-25 8:53 ` [Bug gcov-profile/97193] [9/10/11 Regression] " marxin at gcc dot gnu.org 2020-10-02 10:10 ` cvs-commit at gcc dot gnu.org 2020-10-02 10:11 ` [Bug gcov-profile/97193] [9/10 " marxin at gcc dot gnu.org 2020-10-02 11:16 ` cvs-commit at gcc dot gnu.org [this message] 2020-10-02 11:17 ` cvs-commit at gcc dot gnu.org 2020-10-02 11:18 ` 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-97193-4-jfhBhoY7tl@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).