https://sourceware.org/bugzilla/show_bug.cgi?id=31459
--- Comment #3 from Ruud van der Pas ---
Great to hear this works for you, James!
It is interesting that the outfile option on the collect command was never
documented, but is clearly useful.
The unfortunate thing is that the outfile option as supported on
gp-display-text has a different behaviour:
$ gprofng display text -outfile LOG -limit 5 -functions graph.2.thr.er
Print limit set to 5
$ cat LOG
Functions sorted by metric: Exclusive Total CPU Time
Excl. TotalIncl. Total Name
CPUCPU
sec. %sec. %
15.905 100.00 15.905 100.00
6.464 40.64 6.467 40.66 verify_bfs_tree._omp_fn.0
4.700 29.55 4.716 29.65 make_bfs_tree._omp_fn.0
0.716 4.50 0.716 4.50 mrg_get_uint_orig
0.695 4.37 0.695 4.37 __aarch64_ldadd8_sync
$
As you can see, outfile stores the output from the command, but not the
diagnostics.
This is why it might be cleaner and clearer to introduce a new option on the
gp-collect-app command. Something like -gp-output. It would be the same as
--outfile, but possibly avoid confusion.
Your feedback is much appreciated!
--
You are receiving this mail because:
You are on the CC list for the bug.
