https://sourceware.org/bugzilla/show_bug.cgi?id=32889
Vladimir Mezentsev <vladimir.mezentsev at oracle dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Ever confirmed|0 |1
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed| |2025-04-18
--- Comment #1 from Vladimir Mezentsev <vladimir.mezentsev at oracle dot com>
---
> -With sampling, one inherently profiles a different executable, because
> +With tracing, one inherently profiles a different executable, because
> the calls to the instrumentation library may affect the compiler optimizations
> and run time behaviour.
It can not be affected to the compiler optimizations.
I suggest to remove it:
% git diff gprofng/doc/gprofng_ug.texi
diff --git a/gprofng/doc/gprofng_ug.texi b/gprofng/doc/gprofng_ug.texi
index 714709067d9..f23f7b379ee 100644
--- a/gprofng/doc/gprofng_ug.texi
+++ b/gprofng/doc/gprofng_ug.texi
@@ -310,9 +310,8 @@ Since there is no need to recompile, existing executables
can be used
and the profile measures the behaviour of exactly the same executable that is
used in production runs.
-With sampling, one inherently profiles a different executable, because
-the calls to the instrumentation library may affect the compiler optimizations
-and run time behaviour.
+With tracing, one inherently profiles a different executable, because
+the calls to the instrumentation library may affect runtime behaviour.
@item
With sampling, there are very few restrictions on what can be profiled and
--
You are receiving this mail because:
You are on the CC list for the bug.
