Fix an bug in deoptimization after polymorphic calls in effect contexts.

Fix an bug in deoptimization after polymorphic calls in effect contexts.

For polymorphic calls (also loads and stores) we construct a type switch
graph that has a basic block merging all the variants.  There is an
environment simulation before the goto at the end of all the predecessor
blocks.  This simulation is used to define the environment on entry to the
successor block, and captures the return value of the call.  In effect
contexts, this value should not be present in the environment.

The fix is to use the AST context to decide whether to have this value in
the join node's environment at all.

BUG=1014
Committed: http://code.google.com/p/v8/source/detail?r=6189

[Kevin Millikin (Chromium), 2011-01-05 15:44:59]

There was no bug for stores, because we used an internal AssignmentId that
corresponds to immediately after the assignment (not after the expression).

I'm not thrilled with this as a long-term.  I'd rather get rid of the HSimulate
before every HGoto and the SetJoinId stuff.

[Mads Ager (chromium), 2011-01-05 15:58:12]

LGTM