First draft of translation document

Brian Goetz brian.goetz at
Thu May 20 10:43:52 PDT 2010

VMs maintain many actively managed regions, such as caches for generated code, 
metadata derived from bytecode (such as CFG and SSA reductions), etc, that 
live outside what most java developers think of as "the heap" but don't 
necessarily live in "perm gen."

On 5/20/2010 1:41 PM, Nathan Bryant wrote:
> In that case, if the VM were to decide to generate an optimized
> specialization for a partially applied function, where does the
> generated code go? A MethodHandle may be data, but seems like code is
> code.
> Are you saying the code goes on the normal heap, then?
> -----Original Message-----
> From: Brian Goetz [mailto:brian.goetz at]
> Sent: Thursday, May 20, 2010 1:37 PM
> To: Nathan Bryant
> Cc: Howard Lovatt; lambda-dev at
> Subject: Re: First draft of translation document
>> Can that sort of thing be made safe from a permgen churn perspective?
> Permgen is an issue with nominal class metadata.  But method handle
> activity
> happen in the actively managed memory pools, because method handles are
> anonymous.

More information about the lambda-dev mailing list