On Thu, Aug 8, 2024 at 4:03 AM Wentao Zhang <[email protected]> wrote:
>
> The referenced page contains more explanation of auxname.gcda produced
> by gcov profiler, which is a continuation of -fprofile-arcs's
> description.
OK
> gcc/ChangeLog:
>
> * doc/invoke.texi (Instrumentation Options): Move the cross
> reference of "Cross-profiling" under the description for flag
> "-fprofile-arcs".
> ---
> gcc/doc/invoke.texi | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/gcc/doc/invoke.texi b/gcc/doc/invoke.texi
> index 27539a017..cd10d6cd5 100644
> --- a/gcc/doc/invoke.texi
> +++ b/gcc/doc/invoke.texi
> @@ -17328,6 +17328,8 @@ Note that if a command line directly links source
> files, the corresponding
> E.g. @code{gcc a.c b.c -o binary} would generate @file{binary-a.gcda} and
> @file{binary-b.gcda} files.
>
> +@xref{Cross-profiling}.
> +
> @item -fcondition-coverage
> @opindex fcondition-coverage
> Add code so that program conditions are instrumented. During execution the
> @@ -17336,8 +17338,6 @@ can be used to verify that all terms in a Boolean
> function are tested and have
> an independent effect on the outcome of a decision. The result can be read
> with @code{gcov --conditions}.
>
> -@xref{Cross-profiling}.
> -
> @cindex @command{gcov}
> @opindex coverage
> @item --coverage
> --
> 2.34.1
>
