From: Bernd Edlinger <bernd.edlinger@hotmail.de>
To: Joseph Myers <joseph@codesourcery.com>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
Nathan Sidwell <nathan@acm.org>, Jan Hubicka <hubicka@ucw.cz>
Subject: [PING**3] [PATCH] Force use of absolute path names for gcov
Date: Thu, 01 Jun 2017 15:59:00 -0000 [thread overview]
Message-ID: <AM4PR0701MB216220B276291AC1E587F61DE4F60@AM4PR0701MB2162.eurprd07.prod.outlook.com> (raw)
In-Reply-To: <AM4PR0701MB216233515C810042370F4E13E4E20@AM4PR0701MB2162.eurprd07.prod.outlook.com>
Ping...
On 05/12/17 18:47, Bernd Edlinger wrote:
> Ping...
>
> On 04/28/17 19:41, Bernd Edlinger wrote:
>> Ping...
>>
>> I attached a rebased patch file, with the doc changes and
>> merge conflicts with trunk of today fixed, but otherwise
>> identical.
>>
>>
>> Thanks
>> Bernd.
>>
>> On 04/21/17 22:26, Bernd Edlinger wrote:
>>>
>>>
>>> On 04/21/17 21:50, Joseph Myers wrote:
>>>> On Fri, 21 Apr 2017, Bernd Edlinger wrote:
>>>>
>>>>> So I would like to add a -fprofile-abs-path option that
>>>>> forces absolute path names in gcno files, which allows gcov
>>>>> to get the true canonicalized source name.
>>>>
>>>> I don't see any actual documentation of this option in the patch (you
>>>> add
>>>> it to the summary list of options, and mention it in text under the
>>>> documentation of --coverage, but don't have any actual @item
>>>> -fprofile-abs-path / @opindex fprofile-abs-path paragraph with text
>>>> describing what the option does).
>>>>
>>>
>>> Ah yes, thanks.
>>>
>>> So I'll add one more sentence to invoke.texi:
>>>
>>> @@ -10696,6 +10713,12 @@
>>> generate test coverage data. Coverage data matches the source files
>>> more closely if you do not optimize.
>>>
>>> +@item -fprofile-abs-path
>>> +@opindex fprofile-abs-path
>>> +Automatically convert relative source file names to absolute path names
>>> +in the @file{.gcno} files. This allows @command{gcov} to find the
>>> correct
>>> +sources in projects with multiple directories.
>>> +
>>> @item -fprofile-dir=@var{path}
>>> @opindex fprofile-dir
>>>
>>>
>>>
>>>
>>> Bernd.
next prev parent reply other threads:[~2017-06-01 15:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-21 18:51 Bernd Edlinger
2017-04-21 20:27 ` Joseph Myers
2017-04-21 20:57 ` Bernd Edlinger
2017-04-28 18:14 ` [PING] " Bernd Edlinger
2017-05-12 16:48 ` [PING**2] " Bernd Edlinger
2017-06-01 15:59 ` Bernd Edlinger [this message]
2017-06-01 17:52 ` [PING**3] " Nathan Sidwell
2017-06-01 19:24 ` Bernd Edlinger
2017-06-02 11:35 ` Nathan Sidwell
2017-06-02 14:43 ` Bernd Edlinger
2017-06-05 11:11 ` Nathan Sidwell
2017-06-05 16:31 ` Bernd Edlinger
2017-06-05 19:00 ` Nathan Sidwell
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=AM4PR0701MB216220B276291AC1E587F61DE4F60@AM4PR0701MB2162.eurprd07.prod.outlook.com \
--to=bernd.edlinger@hotmail.de \
--cc=gcc-patches@gcc.gnu.org \
--cc=hubicka@ucw.cz \
--cc=joseph@codesourcery.com \
--cc=nathan@acm.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).