id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc	difficulty
860	C_in_stackp could be optimized	felix winkelmann	felix winkelmann	"There may be situations where an allocation in the nursery exceeds the current stack-limit - the limit is ""soft"", any the check whether the limit is reached does take place only in certain functions and only at the start of a generated C function. Coalescing of allocations and various other factors could create a situation where an object is allocated just slighly above the limit which would trigger a minor GC at the next check but may leave us with an object that is in the nursery but starts outside of the limits. 

Also the use of `C_stack_pointer_test` is not necessary in this function - taking the address of a local would be more than sufficient.
"	enhancement	closed	minor		core libraries	4.7.x	wontfix	C_in_stackp nursery GC