What the JVM needs

From JVMLangSummit
Revision as of 11:57, 28 July 2010 by Jrose (talk | contribs)
Jump to navigationJump to search

Notes from Rich Hickey's workshop

user mode limitations

  • please optimize this
  • fences
  • typestate: now immutable - especially arrays (typically encapsulated in non-writing header, a la java.lang.String)
  • Why Tailcalls: as a guarantee, not just an optimization
  • dynamic vs. inline
  • safepoints


  • fixnums (say, 28-bit small ints encoded as (x >> 28) == -1) http://blogs.sun.com/jrose/entry/fixnums_in_the_vm
  • need a uniform entry/exit types (Object => boxing)
  • Hacker's delight overflow detection is OK (only for add/sub); need a static method that throws overflow-exception?

storage management

  • floating garbage foo(o, o=null); is tailcall a solution?
  • concurrent collection of permgen


  • 31-bit arrays
  • 16-bit instructions
  • static data structures (array literals)


  • structs (efficient pointerless element selection)
  • value types (below)

value types

no mutability, acmp-identity, id-hashcode, monitorenter

  • immutable arrays == array-like value types
  • issue: intermediate early array construction states interact with memory model
  • perhaps need a typestate distinction: under construction vs. immutable