https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105063
--- Comment #7 from Martin Liška <marxin at gcc dot gnu.org> --- (In reply to vit9696 from comment #6) > While true, this scenario is simply inconvenient in many cases. > > (1) When filesystem path limitations exist, they will unavoidably lead to > being unable to save data due to extra large resulting paths. To remind you, > even Windows, a desktop os, had 260 path length limit not so long ago. Sure, well, I can imagine introducing something similar to what we have for gcov: $ gcov --help | grep hash -x, --hash-filenames Hash long pathnames > (2) When analysing gcda files on a different machine one needs to be aware > of the original paths on the machine used for compilation, and we do not > want to require this knowledge. Well, I don't fully understand your needs. On one hand, you're unhappy about the relative placement of the .gcda files. And on the other, you don't like -fprofile-dir=/path. Note you can copy the *.gcda files to an arbitrary location and use it for -fprofile-use=/some/path. That does not require knowledge of -fprofile-generate=/original/path. I'm sorry for defensive argumentation, but believe me the .gcda filename handling is very complex even in the current situation.
