frame deopt handling

[Deneau, Tom]

Graal Hotspot gurus --

I am having trouble finding my way around the frame deoptimization code.  I see where locations are set up for the various locals, expressions, etc. in the ScopeDescs thru our CodeInstaller interfaces but where are those location indicators then read at runtime?

In a similar vein, a routine like frame::local_offset_for_compiler, I didn't see any place that was actually called from?

-- Tom