public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: <David.Taylor@dell.com>
To: <mliska@suse.cz>, <richard.guenther@gmail.com>
Cc: <gcc@gcc.gnu.org>
Subject: RE: gcc: -ftest-coverage and -auxbase
Date: Thu, 20 Jun 2019 16:06:00 -0000	[thread overview]
Message-ID: <8a89e8738dd04141a7bdcf99317755ea@x13pwdurdag1004.AMER.DELL.COM> (raw)
In-Reply-To: <c09adea0-2e6b-b471-589c-dccec54d3d4d@suse.cz>

Dell Customer Communication - Confidential

> From: Martin Liška <mliska@suse.cz>
> Sent: Thursday, June 20, 2019 9:49 AM

> I see. What about the following patch:
> 
> $ ./gcc/xgcc -Bgcc /tmp/main.c --coverage 
> -fprofile-note=/tmp/main.gcno $ ls -l /tmp/main.gcno
> -rw-r--r-- 1 marxin users 428 Jun 20 15:48 /tmp/main.gcno

I haven't tried it.  But, looking it over it looks like it will do everything that I need.  I'll try it and let you know.  Thanks.

  reply	other threads:[~2019-06-20 16:06 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-17 12:46 David Taylor
2019-06-17 13:56 ` Richard Biener
2019-06-17 15:02   ` David.Taylor
2019-06-18  8:40     ` Richard Biener
2019-06-18  8:56       ` Martin Liška
2019-06-18 13:31         ` David.Taylor
2019-06-18 15:19           ` Martin Liška
2019-06-18 21:51             ` David.Taylor
2019-06-19  7:19               ` Martin Liška
2019-06-19 17:11                 ` David.Taylor
2019-06-20  9:11                   ` Martin Liška
2019-06-20 13:00                     ` David.Taylor
2019-06-20 13:02                       ` Thomas Koenig
2019-06-20 13:11                         ` David.Taylor
2019-06-20 13:06                       ` Martin Liška
2019-06-20 13:31                         ` David.Taylor
2019-06-20 13:48                           ` Martin Liška
2019-06-20 16:06                             ` David.Taylor [this message]
2019-06-24 15:59                             ` David.Taylor
  -- strict thread matches above, loose matches on Subject: below --
2019-06-12 20:16 David.Taylor
2019-06-13  8:23 ` Richard Biener

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=8a89e8738dd04141a7bdcf99317755ea@x13pwdurdag1004.AMER.DELL.COM \
    --to=david.taylor@dell.com \
    --cc=gcc@gcc.gnu.org \
    --cc=mliska@suse.cz \
    --cc=richard.guenther@gmail.com \
    /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).