Mark Shannon
Mark Shannon
OOI, what are the other crashes?
[The stats](https://github.com/faster-cpython/benchmarking-public/tree/main/results/bm-20241016-3.14.0a1+-3a126a8) show the expected reduction in misses for `STORE_ATTR_INSTANCE_VALUE`
`DTRACE_FUNCTION_ENTRY()` and `DTRACE_FUNCTION_EXIT()` are **static** instrumentation points for dtrace, are they not? IIUC, this means that they will not work with the JIT. Even if the instrumentation points are compiled...
> For the future, I think we may need extra dtrace point for JIT module How? There's no point in adding back dtrace support for 3.14, if it stops working...
> I'm not sure about the JIT roadmap. if here's more than five years before we make the JIT default release, I think it still is worthed adding the dtrace...
I'm not opposed to having dtrace hooks, but I don't see much value in them unless they * have tests (which means they built in by default, so CI can...
Just to flesh this out a bit: ### Motivation Currently we project traces from the initial hotspot, but there are a number of places in the projection where we would...
@Fidget-Spinner We can keep the switch interpreter working with the tracing JIT using the same technique as we did for `sys.settrace` tracing in 3.11. * Change Tools/cases_generator/analyzer.py to change ENTER_EXECUTOR...
Once https://github.com/python/cpython/pull/140310 is merged, there are a few more tasks to do: - [x] Restore switch based interpreter - [ ] Record values, so we can get rid of the...
https://github.com/python/cpython/issues/141498