[sorry for the late reply]
Thanks Clément for your information.
I have added a slice with your description of the primitive.
https://pharo.fogbugz.com/f/cases/18632/Virtual-Machine-parameters-need-to-be-documented
Can the information about the cache be in the standard image and VM? This would
b
Well the aspects described here either are documented or are being
documented through IWST papers waiting for approval.
The cache accessing technique is detailed in the IWST'16 paper *Inferring
Types by Mining Class Usage Frequency from Inline Caches**. *Hopefully
it'll get accepted and everyone c
clement
you should add that to a simple blog post :)
Stef
Le 24/5/16 à 19:35, Clément Bera a écrit :
Hi,
Sorry the mail is quite long... I CC'd Nevena for section II, she used
the VM caches for type inference.
*
*
*Section I. VM parameters*
*
*
*/46 size of machine code zone, in byt
Thanks Clément for the long description.
I will improve the comments of that method.
Cheers,
Alexandre
> On May 24, 2016, at 1:35 PM, Clément Bera wrote:
>
> Hi,
>
> Sorry the mail is quite long... I CC'd Nevena for section II, she used the VM
> caches for type inference.
>
> Section I. VM
Hi,
Sorry the mail is quite long... I CC'd Nevena for section II, she used the
VM caches for type inference.
*Section I. VM parameters*
* 46 size of machine code zone, in bytes*
Well, the size of the machine code zone :-). To speed-up execution, the cog
uses internally a JIT compiler whic
Hi,
The Cog virtual machine expose some very useful parameters. However, some of
them are a bit obscure to me. For example, what are the following parameters?
What do they mean?
46 size of machine code zone, in bytes
59 number of check event calls since
