<div dir="ltr"><br><div class="gmail_extra"><div class="gmail_quote">On Fri, Jul 3, 2015 at 2:32 AM, Mario Sanchez Prada <span dir="ltr"><<a href="mailto:mario@webkit.org" target="_blank">mario@webkit.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">On 02/07/15 12:11, Mario Sanchez Prada wrote:<br>
> [...]<br>
<span class="">> If you check my last comments in there, you will see that I found out that<br>
> passing -fno-tree-sra to gcc while compiling would reliably prevent the<br>
> crash from happening, both in my use case and when using the URL above.<br>
><br>
> Does anyone here have any idea why this could be the case? Any hint?<br>
><br>
> While passing -fno-tree-sra could be an interesting temporary workaround<br>
> (specially if constrained in scope to bmalloc only) for downstream, it does<br>
> feel like papering over the real issue, which could still be there in WK.<br>
<br>
</span>FWIW, I've tried reducing the scope of this flag to bmalloc but the crash<br>
was still there. However, passing it instead for WebCore only did "fix" the<br>
situation, so perhaps the problem is not strictly related to bmalloc, but to<br>
something else in the graphics subsystem?<br>
<br>
I could also be a bug on GCC, though.<br></blockquote><div><br></div><div>Perhaps you can compare two diassembled bmalloc code with or without -fno-tree-sra since bmallc is a fairly small project?</div><div><br></div><div>- R. Niwa</div><div><br></div></div></div></div>