<html>
<head>
<base href="https://bugs.webkit.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - Offline asm should not output masm assembly when using a x86_64 asm backend"
href="https://bugs.webkit.org/show_bug.cgi?id=162705#c23">Comment # 23</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - Offline asm should not output masm assembly when using a x86_64 asm backend"
href="https://bugs.webkit.org/show_bug.cgi?id=162705">bug 162705</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=162705#c22">comment #22</a>)
<span class="quote">> (In reply to <a href="show_bug.cgi?id=162705#c20">comment #20</a>)
> > If not, then I don't think we should take the patch into trunk, since there
> > would be no way for a WebKit developer to validate whether a change to the
> > code you add would be valid for you. In fact, the new code would be dead
> > code from the standpoint of the WebKit project.
>
> I am in favor of taking this change for the following reasons:
> 1. Visual Studio now ships with a Clang front-end, which I would like to
> start using. The work the Sony people are doing helps in this effort, and
> would save time for me and PerArne.
> 2. I think the amount of 'dead code' we are talking about there is likely to
> be small.
> 3. If we break the Sony build during a period of time that they do not have
> a buildbot, it's on them to track down and fix the problem.
>
> Therefore, I don't see much downside in allow this work to proceed. If it
> becomes a problem, we can roll out the changes in the future.</span >
OK.</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>