https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119553
--- Comment #1 from Jørgen Kvalsvik <j at lambda dot is> ---
Thanks for the report. I think I know what's wrong. When -fpath-coverage (and
really -fprofile-arcs, -fcondition-coverage) is used without -ftest-coverage,
some file output is not enabled. There is a guard for this in profile.cc
(output_to_file) which isn't carried forward to the path coverage functions.
The immediate fix is simple, but I wonder if maybe -fcondition-coverage,
-fpath-coverage should imply -ftest-coverage. Unlike arc profiling it isn't
used for optimization and I don't think it ever makes sense to use
-f{path,condition}-coverage without -ftest-coverage.
