public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Martin Liška" <mliska@suse.cz>
To: David.Taylor@dell.com, richard.guenther@gmail.com
Cc: gcc@gcc.gnu.org
Subject: Re: gcc: -ftest-coverage and -auxbase
Date: Thu, 20 Jun 2019 09:11:00 -0000	[thread overview]
Message-ID: <29b10d2a-2c0d-ad1f-a30a-da655d066d37@suse.cz> (raw)
In-Reply-To: <9132c495211c4db79e52a71bc236ee4c@x13pwdurdag1004.AMER.DELL.COM>

On 6/19/19 7:11 PM, David.Taylor@dell.com wrote:
> Thanks for the patch.  Standalone it is not sufficient.  Combined
> with the other two changes that have been discussed --

Why is that not sufficient? If you build from top-level and you have .o files
that overwrite each other, then you can set -fprofile-note-dir=/tmp/my-unique-folder

And you'll not overwrite .gcno files.

Martin

  reply	other threads:[~2019-06-20  9:11 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 [this message]
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
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=29b10d2a-2c0d-ad1f-a30a-da655d066d37@suse.cz \
    --to=mliska@suse.cz \
    --cc=David.Taylor@dell.com \
    --cc=gcc@gcc.gnu.org \
    --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).