<html>
<head>
<base href="https://bugs.webkit.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - DFG CSE should know how to decay a MultiGetByOffset"
href="https://bugs.webkit.org/show_bug.cgi?id=159859#c2">Comment # 2</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - DFG CSE should know how to decay a MultiGetByOffset"
href="https://bugs.webkit.org/show_bug.cgi?id=159859">bug 159859</a>
from <span class="vcard"><a class="email" href="mailto:fpizlo@apple.com" title="Filip Pizlo <fpizlo@apple.com>"> <span class="fn">Filip Pizlo</span></a>
</span></b>
<pre>(In reply to <a href="show_bug.cgi?id=159859#c1">comment #1</a>)
<span class="quote">> Is MultiGetByOffset not dominated by a StructureCheck the way GetByOffset is?</span >
It's not dominated by a CheckStructure. The MultiGetByOffset does its own structure check.
We want one switch statement that both checks that we have the structure we want and loads the value. CheckStructure with multiple structures in its set will be a switch and MultiGetByOffset is always a switch (unless we failed to strength-reduce a one-case MultiGetByOffset), so that would be two switches. That's not cool, because we can't guarantee that B3 will jump-thread or tail-dup two switches in a row. So, MultiGetByOffset is its own check.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>