Reduce One Caller Inline Max Size to 160 for high optimization levels

[MaxGraey]

Some engines like v8 avoid heavy (large) functions and simply skip optimization for them. To reduce this probability, I propose to slightly decrease the value of OneCallerInlineMaxSize from 200 to 160.

• I've read the contributing guidelines

[dcodeIO]

The PR over there mentions that this is a "short-term mitigation". Do you have a feel for how often we are emitting functions > 500kb with the current thresholds? Would it maybe make sense to add this limit to Binaryen instead, so it can stop inlining when it would reach that size of a function?

[MaxGraey]

500 Kb is very big threshold. But in theory and I do not think that we even at the previous value could exceed it even in the case of some cascade effect. More granular (smaller) functions are good also because they speed up compilation/optimization of binaryen itself.

[MaxGraey]

Would it maybe make sense to add this limit to Binaryen instead, so it can stop inlining when it would reach that size of a function?

@dcodeIO Alan already working on this: WebAssembly/binaryen#3959