You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[wasm] Make jiterpreter module size limit configurable + clean up technical debt (dotnet#107318)
Fix spurious "block stack not empty" errors when an error occurs during jiterp codegen
Add missing overflow checks to blob builder appends
Make maximum trace size a runtime option
Move blob builder capacity to a named constant near the top of the file
// any trace that doesn't have at least this many meaningful (non-nop) opcodes in it will be rejected
143
+
// when deciding whether to generate a trace, we sum the value of sequential opcodes that will fit into it
144
+
// and reject any trace entry point where the score is below this value
144
145
DEFINE_INT(jiterpreter_minimum_trace_value, "jiterpreter-minimum-trace-value", 18, "Reject traces that perform less than this amount of (approximate) work")
145
146
// ensure that we don't create trace entry points too close together
146
147
DEFINE_INT(jiterpreter_minimum_distance_between_traces, "jiterpreter-minimum-distance-between-traces", 4, "Don't insert entry points closer together than this")
0 commit comments