<html>
<head>
<base href="https://bugs.webkit.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - Crash on xLarge memory allocation using bmalloc on 32bit systems"
href="https://bugs.webkit.org/show_bug.cgi?id=146440#c6">Comment # 6</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - Crash on xLarge memory allocation using bmalloc on 32bit systems"
href="https://bugs.webkit.org/show_bug.cgi?id=146440">bug 146440</a>
from <span class="vcard"><a class="email" href="mailto:mario@webkit.org" title="Mario Sanchez Prada <mario@webkit.org>"> <span class="fn">Mario Sanchez Prada</span></a>
</span></b>
<pre>(In reply to <a href="show_bug.cgi?id=146440#c4">comment #4</a>)
<span class="quote">> [...]
> What about setting this flag only for the bmalloc source files at
> Source/bmalloc/CMakeLists.txt . Would it be enough?</span >
Not sure, but I will try that out just in case, I'd rather keep compiler optimizations enabled whenever/wherever possible. Thanks for the suggestion.
(In reply to <a href="show_bug.cgi?id=146440#c5">comment #5</a>)
<span class="quote">> I think it'd be best to patch this downstream, unless we start getting
> additional bug reports; since you're the only one to have needed it so far,
> I guess it has likely already been fixed in GCC.</span >
Not sure about this. While I understand this is a workaround and not the proper solution, this issue is not present just in our platform (where we use gcc 4.9) but also in Fedora, as you pointed out before, where you're using gcc 5.1.
The main difference between Fedora and our platform so far seems to be how likely the crash would happen. In our case it was happening always and that's why, even being quite sneaky, I managed to found a solution for it after all. But in other systems this can be very tricky to investigate, so perhaps it would be better to include the patch upstream, so that every single user would benefit of it?
Not 100% sure, would like to hear more opinions on this.
<span class="quote">> Good job finding the exact optimization at fault; I don't want to think
> about how long you spent compiling. :(</span >
Thanks. In the end it was not that terrible, the hardest part was before I stopped trying to debug the code and started looking at the compiler's optimizations. Once I figure out that -O1 would "cause" the crash, it was all much more simple :)</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>