public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "sandra at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug gcov-profile/94029] [9 Regression] gcc crash in coverage.c:655 since r9-4216-g390e529e2b98983d
Date: Tue, 24 Mar 2020 22:29:17 +0000	[thread overview]
Message-ID: <bug-94029-4-b3HxUNQ8EV@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-94029-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94029

--- Comment #18 from sandra at gcc dot gnu.org ---
I'm seeing the missing gcov file on nios2-linux-gnu as well.  Git revision
6e00d8dcf32ace6588a1a4843dfcc0e8b9f9d00f.

I took another look at the testcase.  I haven't used gcov for about a gazillion
years, but...

It says "{ dg-do compile }".  Don't you have to run the testcase to collect the
data to run with gcov?  And copy the .gcda file from the target to the host?

Then, it is trying to run "gcov gcov-pr94029.c" instead of e.g. "nios2-elf-gcov
gcov-pr94029.c", and it's picking up some random gcov program installed on the
host system instead of the one for the target.

Maybe this testcase should just be restricted to native targets?

  parent reply	other threads:[~2020-03-24 22:29 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-94029-4@http.gcc.gnu.org/bugzilla/>
2020-03-12 11:58 ` [Bug gcov-profile/94029] [9/10 " jakub at gcc dot gnu.org
2020-03-17 16:23 ` marxin at gcc dot gnu.org
2020-03-17 16:43 ` marxin at gcc dot gnu.org
2020-03-18 12:40 ` jakub at gcc dot gnu.org
2020-03-18 12:51 ` marxin at gcc dot gnu.org
2020-03-18 13:04 ` jakub at gcc dot gnu.org
2020-03-19 21:57 ` cvs-commit at gcc dot gnu.org
2020-03-19 21:58 ` [Bug gcov-profile/94029] [9 " jakub at gcc dot gnu.org
2020-03-22  4:57 ` sandra at gcc dot gnu.org
2020-03-22  5:24 ` bernd.edlinger at hotmail dot de
2020-03-23 18:46 ` cvs-commit at gcc dot gnu.org
2020-03-24 22:29 ` sandra at gcc dot gnu.org [this message]
2020-03-25  0:00 ` bernd.edlinger at hotmail dot de
2020-04-07 19:03 ` cvs-commit at gcc dot gnu.org
2020-04-07 19:03 ` cvs-commit at gcc dot gnu.org
2020-04-07 20:00 ` jakub 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-94029-4-b3HxUNQ8EV@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: link
Be 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).