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: Joe Buck <Joe dot Buck at synopsys dot COM>
- To: Gabriel Dos Reis <gdr at integrable-solutions dot net>
- Cc: Mark Mitchell <mark at codesourcery dot com>, gcc at gcc dot gnu dot org,Nathan Sidwell <nathan at codesourcery dot com>
- Date: Fri, 25 Mar 2005 09:47:20 -0800
- Subject: Re: Profile-directed feedback and remote testing
- References: <4243C4FB.8090000@codesourcery.com> <m3hdj084pp.fsf@uniton.integrable-solutions.net>
Mark Mitchell <mark@codesourcery.com> writes:
> | 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 had just that problem the other day, when a colleague asked me to help
him debug a problem. Since his executable was set up to generate gcov
data, I couldn't run it as I didn't have permission to write his count
files, and he'd left for the day, so I couldn't get him to change the
permissions. I wound up rebuilding the whole large executable from
source, but that was an annoying waste of time.
On Fri, Mar 25, 2005 at 10:17:22AM +0100, Gabriel Dos Reis wrote:
> Maybe an option to tell the compiler where to put thos .gcda files?
That wouldn't have saved me in the case described above, as the pathnames
are already set in the executable. A *runtime* way of altering the
locations of the .gcda files would be nice to have. For example, we could
have something like
GCDA_PATH_PREFIX
which, if set, would be prepended to the pathnames of the .gcda files.
We could even arrange to create needed directories on demand when
creating new .gcda files when this option is set.