[Vm-dev] Why primitive new have unexpected temp affectation

Mathieu Suen mathk.sue at gmail.com
Mon Aug 13 11:23:18 UTC 2007

On Aug 13, 2007, at 10:08 AM, Adrian Lienhard wrote:

> Hi Mathieu,
> Not sure if I understand you correctly. Do you mean, why  
> stackValue: 1 is read twice?
> The reason for this is because  
> #sufficientSpaceToInstantiate:indexableSize: may trigger GC (as the  
> comment says), and therefore the temp pointer to the class, which  
> is read before, may not be valid anymore.

Why the  GC need to change the temp pointer?

More information about the Vm-dev mailing list