https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87553
--- Comment #7 from Martin Liška <marxin at gcc dot gnu.org> --- (In reply to r...@cebitec.uni-bielefeld.de from comment #6) > > --- Comment #5 from Martin Liška <marxin at gcc dot gnu.org> --- > [...] > >> Sorry, I've been doing too many things at once and not been paying close > >> enough attention. Besides, the g++.log file lacks the "spawn ..." line > >> for executing the binary, so I missed this (obvious) step. > > > > That's true, but it should only run the executable without arguments. > > Indeed: it's easy if you don't forget the step ;-) > > >> Whatever, when I run the executable, inline_mismatch_args.gcda *is* > >> generated. Still, when I run the -fprofile-use step, I get the warnings > >> reported. > > > > Then it's hard to guess.. > > I've now checked the .gcda file on Solaris 11 where things work fine: > it's the same size (312 bytes) and both files barely differ: > > $ cmp -l inline_mismatch_args.gcda.s10 ~/inline_mismatch_args.gcda.s11 > 10 2 64 > 11 316 0 > 12 333 202 You can use gcov-dump -l to dump content of the files. However, it's not problem as the file exists. The warning should be only shown when a checksum of a source file changes or *.gcda file is missing.
