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/102746] gcov returns 0 un erroneuos incovation Date: Mon, 18 Oct 2021 11:13:45 +0000 [thread overview] Message-ID: <bug-102746-4-dzQQEiSxKB@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-102746-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102746 --- Comment #5 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:815f15d3384edbdd73cc54536f30947e15183151 commit r12-4474-g815f15d3384edbdd73cc54536f30947e15183151 Author: Martin Liska <mliska@suse.cz> Date: Mon Oct 18 11:30:55 2021 +0200 gcov: return proper exit code when error happens PR gcov-profile/102746 PR gcov-profile/102747 gcc/ChangeLog: * gcov.c (main): Return return_code. (output_gcov_file): Mark return_code when error happens. (generate_results): Likewise. (read_graph_file): Likewise. (read_count_file): Likewise.
next prev parent reply other threads:[~2021-10-18 11:13 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-10-14 14:44 [Bug gcov-profile/102746] New: " chipitsine at gmail dot com 2021-10-14 15:12 ` [Bug gcov-profile/102746] " marxin at gcc dot gnu.org 2021-10-14 15:17 ` chipitsine at gmail dot com 2021-10-15 6:32 ` chipitsine at gmail dot com 2021-10-15 8:20 ` marxin at gcc dot gnu.org 2021-10-15 8:20 ` marxin at gcc dot gnu.org 2021-10-18 11:13 ` cvs-commit at gcc dot gnu.org [this message] 2021-10-18 11:14 ` marxin at gcc dot gnu.org 2021-10-18 12:11 ` chipitsine at gmail dot com 2021-10-18 12:17 ` marxin at gcc dot gnu.org 2021-10-18 12:30 ` chipitsine at gmail dot com 2021-10-19 12:56 ` 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-102746-4-dzQQEiSxKB@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).