<html>
<head>
<base href="https://bugs.webkit.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - DFG peephole does not have effect on CompareEq / CompareStrictEq because of MovHint"
href="https://bugs.webkit.org/show_bug.cgi?id=149713#c1">Comment # 1</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - DFG peephole does not have effect on CompareEq / CompareStrictEq because of MovHint"
href="https://bugs.webkit.org/show_bug.cgi?id=149713">bug 149713</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>When and if we implement a fix that allows the peephole detection to "skip" the MovHint, we should check how much of a speed-up it is.
If it is not a speed-up, then instead of writing a patch that extends the peephole to skip MovHint, we should write a patch that removes all code for those peepholes that are currently dead because of the MovHint. That peephole code is a pain to maintain and it's possible that it buys us nothing.</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>