RESOLVED FIXED Bug 97162
OSR exit sometimes neglects to create the arguments object
https://bugs.webkit.org/show_bug.cgi?id=97162
Summary OSR exit sometimes neglects to create the arguments object
Geoffrey Garen
Reported 2012-09-19 19:08:59 PDT
OSR exit sometimes neglects to create the arguments object
Attachments
Patch (16.48 KB, patch)
2012-09-19 19:43 PDT, Geoffrey Garen
no flags
Patch (16.64 KB, patch)
2012-09-19 19:53 PDT, Geoffrey Garen
fpizlo: review+
Geoffrey Garen
Comment 1 2012-09-19 19:43:02 PDT
Gyuyoung Kim
Comment 2 2012-09-19 19:47:43 PDT
Geoffrey Garen
Comment 3 2012-09-19 19:53:46 PDT
Filip Pizlo
Comment 4 2012-09-19 20:54:29 PDT
Comment on attachment 164828 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=164828&action=review Your call on the hash traits thingy. I think they might be useful in other cases, too, so having them in the DFG, and particularly in the header of one phase of the DFG, seems awkward. But I can't bring myself to care too much. > Source/JavaScriptCore/dfg/DFGArgumentsSimplificationPhase.h:44 > +template<typename T> > +struct NullableHashTraits : public HashTraits<T> { > + static const bool emptyValueIsZero = false; > + static T emptyValue() { return reinterpret_cast<T>(1); } > +}; > + It's not a big deal but it would be super fabulous if this was in HashTraits.h.
Filip Pizlo
Comment 5 2012-09-19 20:56:12 PDT
Comment on attachment 164828 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=164828&action=review > Source/JavaScriptCore/dfg/DFGArgumentsSimplificationPhase.cpp:434 > || unmodifiedArgumentsRegister(m_graph.argumentsRegisterFor(node.codeOrigin)) == variableAccessData->local()) { > - // The child of this store should really be the empty value. > - Node emptyJSValue(JSConstant, node.codeOrigin, OpInfo(codeBlock()->addOrFindConstant(JSValue()))); > - emptyJSValue.ref(); > - NodeIndex emptyJSValueIndex = m_graph.size(); > - m_graph.deref(node.child1()); > - node.children.child1() = Edge(emptyJSValueIndex); > - m_graph.append(emptyJSValue); > - insertionSet.append(indexInBlock, emptyJSValueIndex); > - changed = true; > break; > } Doesn't this create one of those situations where we would omit the { and }? I think style checker is agnostic since the if itself spans two lines. I would drop the { and }. But it's not a big deal.
Geoffrey Garen
Comment 6 2012-09-19 21:05:06 PDT
> It's not a big deal but it would be super fabulous if this was in HashTraits.h. Will do. > Doesn't this create one of those situations where we would omit the { and }? You're right. Will fix.
Geoffrey Garen
Comment 7 2012-09-19 21:44:10 PDT
Note You need to log in before you can comment on or make changes to this bug.