Need more non-escaping specializations

[Fidget-Spinner]

Right now I'm working on function inlining. The inlining works by optimistically attempting to inline any function whose entire body is non-escaping.

The problem is that operations such as // or ** seem innocuous enough, but are unspecialized and so cannot be differentiated from an overloaded binary op. These things exist in bm_chaos and bm_spectralnorm. They thus block inlining of really simple small functions.

For now, I shall just add specializations for them on my branch for the sake of benchmarking, but in the long term, we need some way to collect this profiling information and reflect that to tier 2. Something like what @markshannon suggested about some sort of dispatch table for infrequent and the long tail of specializations maybe?

[CCLDArjun]

For now, I shall just add specializations for them on my branch for the sake of benchmarking

Why not merge these in? There are already specializations for other binary ops like multiply, add and subtract so we can add some for // and ** too, right?

[Fidget-Spinner]

Why not merge these in?

Interpreter opcodes are a limited resource.

Closing this, as it's handled by python/cpython#128722.