Jason Gloudon wrote: > ptrdiff_t is not a pointer type, so cur_var_ptr + PARROT_PTR_ALIGNMENT skips > exactly PARROT_PTR_ALIGNMENT bytes. I did modify your patch slightly - reversed directions (top->down is probably more common) - increment by sizeof(void*) This boost life.pasm gens from 270 -> 330 The I did apply #17495 again: 330 -> 403 WRT the latter: It was considered unsafe to put lo_var_ptr just above the run_loop. I still don't see an example for this. It could be a src test, which first tests some PMC stuff, the runs an interpreter and finally checks PMCs again. To be safe, we could do: if (!interpreter->lo_var_ptr) interpreter->lo_var_ptr = &lo_var_ptr; Default is not to set it early, so interpreter->lo_var_ptr would always be near the run loop. This applies of course to all cores. (All tests still succeed --gc-debug) leoThread Previous | Thread Next