<html>
<head>
<base href="https://bugs.webkit.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - NewRegexp should not prevent inlining"
href="https://bugs.webkit.org/show_bug.cgi?id=154808#c11">Comment # 11</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - NewRegexp should not prevent inlining"
href="https://bugs.webkit.org/show_bug.cgi?id=154808">bug 154808</a>
from <span class="vcard"><a class="email" href="mailto:ticaiolima@gmail.com" title="Caio Lima <ticaiolima@gmail.com>"> <span class="fn">Caio Lima</span></a>
</span></b>
<pre>(In reply to <a href="show_bug.cgi?id=154808#c10">comment #10</a>)
<span class="quote">>
> There's a lot of logic there:
>
> - Freezing causes the resulting CodeBlock to have either a strong or weak
> reference to the frozen object, depending on whether you froze it strongly
> or weakly.
>
> - Freezing immediately causes the ongoing DFG compilation plan to track the
> reference if a GC happens while the compiler is running. The GC knows how
> to safepoint the compiler. This means that from the compiler's standpoint,
> GCs can only happen at well-defined points: either before the compiler
> started, during B3 compilation, or after the compiler finished.
>
> There are a lot of other details; I can't remember all of them off the top
> of my head. The short version is just: we already use freezing a lot, and
> it's designed exactly for what you want: you have some object that the
> generated code will refer to and you want to make sure that this object gets
> marked.</span >
Thank You so much.</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>