pystats: Improve with JIT builds

Feature or enhancement

Proposal:

At the moment, not all pystats work for a JIT build. This is mostly because certain stat collections exist in the Tier 2 interpreter loop, not in the bytecode instructions themselves. The reason for having parity in the stats is not so much that we expect the numbers to be different vs. a Tier 2 run, but because it would be nice to add some JIT-specific stats (e.g. a code size histogram) and the only way to do that now would be to collect stats twice and combine them.

A list of what's missing:

• traces executed
• uops executed
• trace run length histogram
• uop execution stats

I'm volunteering to do the work, but maybe @brandtbucher could confirm this makes sense?

Has this already been discussed elsewhere?

No response given

Links to previous discussion of this feature:

No response

Linked PRs

• gh-117346