3 ms·

It's not clear to me how this would track stack<->stack and memory<->stack copies. Can you explain?

• throwup 4y ago
  My suggestion would not measure the copies themselves, but it would count how many bytes are the source/destination of copies (of course incl. other things like parameters/etc). It's not the exact same metric, but it does still help answer the question in the title. I would expect the two numbers to be highly correlated when building the same binary with different versions of the compiler. It would also solve some practical problems mentioned in the page like the complexity of the setup and the speed of statistics gathering.
• toxik 4y ago
  If you copy between stack regions, you need more stack memory, so the stack allocation should be larger. Of course, this would undercount cases that copy to the same region many times which seems likely.