Re: [Valgrind-users] RFC: proposal to remove user annotation from `cg_annotate`

2023-04-03 Thread Nicholas Nethercote
There were no objections, and I have now removed user annotations from `cg_annotate`. Nick On Wed, 29 Mar 2023 at 09:03, Nicholas Nethercote wrote: > Hi, > > I recently rewrote `cg_annotate`, `cg_diff`, and `cg_merge` in Python. The > old versions were written in Perl, Perl, and C, respectively

Re: [Valgrind-users] RFC: changing Cachegrind default to `--cache-sim=no`

2023-04-03 Thread Nicholas Nethercote
On Mon, 3 Apr 2023 at 21:36, David Faure wrote: > > But then, what's the difference between `cachegrind --cache-sim=no` > and `callgrind`? > > https://accu.org/journals/overload/20/111/floyd_1886/ says > "The main differences are that Callgrind has more information about the > callstack whilst ca

Re: [Valgrind-users] RFC: changing Cachegrind default to `--cache-sim=no`

2023-04-03 Thread David Faure
[removing valgrind-developers, since I guess I can't post there] On lundi 3 avril 2023 11:29:25 CEST Nicholas Nethercote wrote: > I have been using `--cache-sim=no` almost exclusively for a long time. The > cache simulation done by Valgrind is an approximation of the memory > hierarchy of a 2002 A

[Valgrind-users] RFC: changing Cachegrind default to `--cache-sim=no`

2023-04-03 Thread Nicholas Nethercote
Hi, Cachegrind has an option `--cache-sim`. If you run with `--cache-sim=yes` (the default) it tells it Cachegrind to do a full cache simulation with lots of events: Ir, I1mr, ILmr, Dr, D1mr, DLmr, Dw, D1mw, DLmw. If you run with `--cache-sim=no` then the cache simulation is disabled and you jus