This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Profile-directed feedback and remote testing
- From: Daniel Jacobowitz <drow at false dot org>
- To: gcc at gcc dot gnu dot org
- Date: Fri, 25 Mar 2005 09:07:13 -0500
- Subject: Re: Profile-directed feedback and remote testing
- References: <4243C4FB.8090000@codesourcery.com>
On Thu, Mar 24, 2005 at 11:59:55PM -0800, Mark Mitchell wrote:
> When we generate data for feedback, we insert the .gcda name into the
> object file as an absolute path. As a result, when we try to do remote
> testing, we lose, as, in general the remote file system does not have
> the same file hierarchy as the build system.
>
> I understand why we generate an asbolute path; we want to make sure that
> the data ends up there, not in the directory where the user happens to
> run the program. So, I intend to disable these tests when $host !=
> $target. Any objections, or better ideas?
It would be nice if we could preserve the ability to run them - when
your build directory is mounted on the target system at the same path,
the tests will pass. Perhaps a compiler option, as Gabriel
suggested...
--
Daniel Jacobowitz
CodeSourcery, LLC