From: Martin Thuresson <martint@google.com>
To: "kai.tietz@onevision.com" <kai.tietz@onevision.com>,
gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: PR 47793 - Support relative paths using -fprofile-generate
Date: Thu, 24 Feb 2011 00:56:00 -0000 [thread overview]
Message-ID: <AANLkTinDEr9k0GGgaJHbYSjuLwcSu6gB=HKn12G0bx0z@mail.gmail.com> (raw)
In-Reply-To: <AANLkTi=B8wq3uxBP3Kzk3jGw6Rn=jAjf6oAhFG_jqxj8@mail.gmail.com>
On Wed, Feb 23, 2011 at 10:21 AM, Martin Thuresson <martint@google.com> wrote:
> Change 165596 and 168475 updated the code for handling gcda-paths. As
> part of this change, relative paths stopped working.
>
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47793
>
> This patch adds a guard so that "/" is not added when no prefix is
> given.
>
> The added testcase uses the path "../gcc/". This puts the gcda in the
> same directory, so that the cleanup-coverage-files will find them.
>
> I have tested the patch using "make bootstrap; make -k check" with
> target x86_64-unknown-linux-gnu and saw no additional test failures.
>
> Let me know if there is any other testing I should do.
ChangeLog
gcc/
2011-02-23 Martin Thuresson <martint@google.com>
PR gcov-profile/47793
* libgcov.c (gcov_exit): Support relative profile paths.
gcc/testsuite/
2011-02-23 Martin Thuresson <martint@google.com>
PR gcov-profile/47793
* gcc.dg/pr47793.c: New.
>
> Thanks,
> Martin
>
next prev parent reply other threads:[~2011-02-23 23:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AANLkTimkRXMEH5QzVpcaxNZMaK=CE-w7tAXF=1yxQxNZ@mail.gmail.com>
2011-02-23 18:33 ` Martin Thuresson
2011-02-24 0:56 ` Martin Thuresson [this message]
2011-03-01 22:08 ` Martin Thuresson
2011-03-07 19:54 ` Diego Novillo
2011-03-08 5:25 ` Martin Thuresson
2011-05-04 23:53 ` Xinliang David Li
2011-05-06 18:06 ` Xinliang David Li
2011-05-13 9:08 ` Jan Hubicka
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='AANLkTinDEr9k0GGgaJHbYSjuLwcSu6gB=HKn12G0bx0z@mail.gmail.com' \
--to=martint@google.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=kai.tietz@onevision.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).